Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MacRumors

macrumors bot
Original poster
Apr 12, 2001
68,643
39,518


Following the launch of iOS 16.3.1 on February 13, Apple is no longer signing iOS 16.3, the previously available version of iOS. Now that Apple has stopped signing iOS 16.3, it is no longer possible to downgrade to that version of iOS after installing the iOS 16.3.1 update.

iOS-16.3-Feature-Red.jpg

Apple routinely stops signing older versions of iOS after new releases come out in order to encourage customers to keep their operating systems up to date, so it is not unusual that the iOS 16.3 update is no longer being signed.

iOS 16.3 was a relatively minor update that introduced support for physical security keys for Apple IDs, expanded Advanced Data Protection globally, added support for the second-generation HomePod, and more.

While iOS 16.3.1 remains the current public version of iOS, Apple released the first beta of iOS 16.4 last week with support for new emoji characters, web push notifications, and more.

(Thanks, Aaron!)

Article Link: Apple Stops Signing iOS 16.3 Following iOS 16.3.1 Launch, Downgrading No Longer Possible
 
  • Sad
Reactions: sorgo †
It's fine for millions of users.
One death is a tragedy, one million deaths is a statistic.

If you're the one person affected by the bug introduced in the newest OS, the newest OS is hot garbage in your eyes.

I don't like how Apple refuses to allow downgrades, especially when their upgrade screws something up.
 
One death is a tragedy, one million deaths is a statistic.

If you're the one person affected by the bug introduced in the newest OS, the newest OS is hot garbage in your eyes.

I don't like how Apple refuses to allow downgrades, especially when their upgrade screws something up.
The issue is most people are horrendously bad at diagnosing complex issues. It's easy to blame 16.3.1 when it could be a whole host of issues. I worked on the Android ROM Development side of things and it was hilarious how people would blame bugs on nightly builds despite no commits in the past 48 hours. And then when there are commits, it's frequently translation updates only and all of a sudden you get battery posts about how the latest build makes a night and day difference.

  • An update usually is accompanied by a reboot so all sorts of things can change even with a reboot (see this whole android ROM development scene story above... I suspect 99% of people seeing battery issues would see battery life change with a reboot whether or not they update their OS or not)
  • 99% of blaming new builds never tries to revert to an older build to compare the difference. New York Times addresses this as confirmation bias which is a huge problem in almost all problem solving. Everyone likes to claim how they can "reproduce the bug," which is fine, but if you claim to know what causes the bug the you in theory can also turn off that bug. Most people, even some of the brightest engineers probably at Apple are capable of showing what causes the bug, but since it takes time to run a new experiment to see how you can turn OFF the bug, most people skip that and assume they have a solution (see NYT problem)
  • People facing bugs typically blame the wrong thing (update) when you can likely reproduce their issues on another build as well.
I'm not trying to diminish anyone's problems with their devices, but I do feel that "latest version bug bias" is a real placebo effect.
 
Last edited:
Makes no sense since 16.3.1 is hot garbage
How so? Runs fine for me and zillions of others. Only you seem to be outraged by 16.3.1. To make such a claim without any proof indicates causes complete lack of credibility. Unfortunately, there is only the ignore file for this kind of garbage. I wish there was a triple ignore file. Oh, and those that liked your comment are also now in the ignore file. I just don't understand why the hot garbage supporters are Apple hardware and software.
 
One death is a tragedy, one million deaths is a statistic.

If you're the one person affected by the bug introduced in the newest OS, the newest OS is hot garbage in your eyes.

I don't like how Apple refuses to allow downgrades, especially when their upgrade screws something up.
At this point. They might value security over bugs for some users.
 
  • Like
Reactions: SFjohn
One death is a tragedy, one million deaths is a statistic.

If you're the one person affected by the bug introduced in the newest OS, the newest OS is hot garbage in your eyes.

I don't like how Apple refuses to allow downgrades, especially when their upgrade screws something up.
No software will work 100% for a 100% of users. If you’re the one that feels that iOS is hot garbage there is competition.

And downgrades are just that…downgrades in every sense.
 
  • Love
Reactions: SFjohn
Given this is 1 week after release of 16.3.1, is the typical time frame to allow people to downgrade for 1 week and then stop signing the previous version? I've never downgraded before but I'd like to know what the signing timeframe is should I need that ability.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.