Apple ceases signing of iOS 10.3.1 after release of iOS 10.3.2

Apple on Tuesday stopped signing code for iOS 10.3.1, halting downloads and installations of the legacy operating system in favor of iOS 10.3.2.

As usual, the move comes over one month after Apple issued iOS 10.3.2 in May. The most recent iOS revision was released publicly after a month-long beta period, and contains only minor bug fixes and performance improvements.

Apple regularly stops signing code to prevent users from installing old iOS versions following the release of a new OS release. The strategy is employed as a security measure, ensuring users have the most up-to-date software running on their iPhone, iPad and iPod device. A halt to code signing also helps ease potential compatibility issues with new features and software.

After today, users can only download and install iOS 10.3.2 from Apple's servers.

Apple is already well into testing of its next iOS 10 version, iOS 10.3.3, which will deliver the usual bug patches to consumers prior to this fall's launch of iOS 11.

Unlike recent maintenance updates, iOS 11 incorporates a bevy of user-facing improvements and backend enhancements to Siri, Apple Pay, Photos and other first-party apps and services. The upcoming release packs in a boatload of new features for iPad, including drag-and-drop multitasking, deeper Apple Pencil integration and more.

For more information on iOS 11, make sure to check out AppleInsider's "Inside iOS 11" series.

4 Comments

alexmit 112 comments · 13 Years

About 7 years ago

10.3.2 is a battery killer in several iPhones I have seen. Maybe it was a carrier update. I live close to a tower and have had full signal for years. 10.3.2 seems to have impaired that signal. It seems to have also impaired the WiFi signal for some reason, in turn killing my battery at a 40% quicker rate than before the update.

lkrupp 10521 comments · 19 Years

alexmit said:

10.3.2 is a battery killer in several iPhones I have seen. Maybe it was a carrier update. I live close to a tower and have had full signal for years. 10.3.2 seems to have impaired that signal. It seems to have also impaired the WiFi signal for some reason, in turn killing my battery at a 40% quicker rate than before the update.

Just stifle it. Every iOS update begets a rash of “battery killer” reports from users. You need to investigate what is causing the problem (hint: it’s not iOS 10.3.2) A good source is iMore which has several articles on how to track down battery issues.

MplsP 4018 comments · 8 Years

lkrupp said:

Just stifle it. Every iOS update begets a rash of “battery killer” reports from users. You need to investigate what is causing the problem (hint: it’s not iOS 10.3.2) A good source is iMore which has several articles on how to track down battery issues.

Yes, and plenty of people have gone through those articles, taken all the advice and are still having battery issues that magically appeared after updating from iOS 10.3.1 to 10.3.2 If nothing else has changed then how do you blame something else? And no, not every update has widespread complaints of issues with battery life.

foggyhill 4767 comments · 10 Years

MplsP said:

lkrupp said:

Just stifle it. Every iOS update begets a rash of “battery killer” reports from users. You need to investigate what is causing the problem (hint: it’s not iOS 10.3.2) A good source is iMore which has several articles on how to track down battery issues.

Yes, and plenty of people have gone through those articles, taken all the advice and are still having battery issues that magically appeared after updating from iOS 10.3.1 to 10.3.2 If nothing else has changed then how do you blame something else? And no, not every update has widespread complaints of issues with battery life.

- IOS could have reset its settings (need to set them back)
- Apps could have had reset settings, like push notifications (need to set them back)
- IOS update could have triggered APPS updates
- IOS update maybe had to index everything through spotlight or host of other system background tasks.
- IOS could have cleared some system or apps caches meaning them all need to be redownloaded
- IOS could need to resync with Icloud, or redownload apps if it needed to shunt them off to update
- Apps themselves could have bugs revealed by IOS 10
- Battery charge, discharge calibration could be out of wack (the 0 and 100% it has doesn't correspond with actual battery state) (usually a full discharge until shutdown, then full charge and then again full discharge till shutdown, fixes this).
etc. This has happened in quite a few updates.

None of these things are caused by bugs in IOS 11 yet they all use the battery.

About 35% of all updates have many people claiming "battery kill", that you claim otherwise means your not really paying attention
This mostly occur in the first 1-2 weeks after the update and resorbs itself naturally without Apple really doing anything in most cases.
Look at your apps first (have their settings been reset); then look for reset settings in the OS itself, then if it needed to reindex spotlight, redownload apps, whatever.