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,630
39,510



IPSW-250x250.png
Following the release of iOS 13.2 on October 28, Apple today stopped signing iOS 13.1.3, which means downgrading to this version of iOS is no longer possible.

iOS 13.1.3 was a minor update released in mid-October with bug fixes for issues with Phone, Mail, Health, iCloud, and more.

Apple routinely stops signing older versions of software updates after new releases come out in order to encourage customers to keep their operating systems up to date. Apple has also stopped signing iOS 13.1.2, which was another minor bug fix update.

iOS 13.2 is the current public version of iOS, and it brought support for AirPods Pro, included new emojis, added Deep Fusion for the iPhone 11 and 11 Pro, and more.

Developers and public beta testers can also download iOS 13.3, an upcoming update that introduces Communication Limits for Screen Time.

Article Link: Apple Stops Signing iOS 13.1.2 and iOS 13.1.3 Following the Release of iOS 13.2
 
What I would give to rollback to iOS 12 without loosing data. Multitasking is a joke on 13.2. Music app crashes 5+ times a day. Safari freezes every time I scroll. Phones hot enough to cook and egg, 50% battery by 11am. Just beyond a joke.
Just out of curiosity, what iPhone model are you experiencing this on?
 
  • Like
Reactions: Dj64Mk7
Hey there you go, pay to install a previous iOS version. I think Apple is missing out on a hidden revenue stream.
 
  • Like
Reactions: Sasparilla
Probably getting ready to release 13.2.2 tomorrow. They didn’t want to have 4 signed versions going at once.
 
  • Like
Reactions: max2
Really Apple? Stopped signing the last builds that didn’t break multitasking. Can’t make this **** up. Who the hell is in charge over there?
Calm down. 13.3 fixes it and the beta is available now. I’m running it and multitasking has been fixed, which was a HUGE issue for me in 13.2.

This wasn’t ideal, but try to remain calm. They didn’t break it on purpose and it seemingly doesn’t impact everyone. There might be security reasons or other reasons to not sign older versions.
 
Just out of curiosity, what iPhone model are you experiencing this on?

iPhone XS - 2 months old.
I even have all my music offline. Apple Music seems to be a massive battery hog “background activity” has consumed 40% today. Listening to music ~1hr with screen off. Absolute joke. Guess the alternative is to switch to Spotify.
 
iPhone XS - 2 months old.
I even have all my music offline. Apple Music seems to be a massive battery hog “background activity” has consumed 40% today. Listening to music ~1hr with screen off. Absolute joke. Guess the alternative is to switch to Spotify.
You shouldn‘t even have to explain that. Any model that received an update should not have inferior performance on new software while not changing the workflow. It‘s just lazy a** programming and poor QA that led us here. But it‘s nothing new anyway.
 
Not fair. Apple knows about iOS 13.2 issues, so why stop signing the last working version ?

Cause nobody at the decision level was on top of it enough to say and move forward with the "maybe we shouldn't stop signing 13.1.x until we've got a version out that fixes 13.2's single tasking issues..".
 
Calm down. 13.3 fixes it and the beta is available now. I’m running it and multitasking has been fixed, which was a HUGE issue for me in 13.2.

This wasn’t ideal, but try to remain calm. They didn’t break it on purpose and it seemingly doesn’t impact everyone. There might be security reasons or other reasons to not sign older versions.
Don’t tell people to calm down guy. This is another instance of Apple screwing up big time. This was reported during 13.2 beta and was not addressed. Inexcusable.

Also, I don’t care if it’s fixed in a beta. I’m not going to test beta software for anyone for free ever again.

Apple cared more about pushing out 13.2 than delivering a quality release.
 
Don’t tell people to calm down guy. This is another instance of Apple screwing up big time. This was reported during 13.2 beta and was not addressed. Inexcusable.

Also, I don’t care if it’s fixed in a beta. I’m not going to test beta software for anyone for free ever again.

Apple cared more about pushing out 13.2 than delivering a quality release.
Stop overreacting. I was impacted by it too. Not sure how it’s inexcusable to make mistakes in software development. It happens and Apple has a great track record fixing issues and releasing updates.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.