Apple stopped signing iOS 15 for iPhone 13 series so possible a new build is coming
Hopefully.15.0.1 inbound today then! 🤔🤓
What makes you think it should drop by 1%? I don't think I've ever had a mobile phone that consistently drops by 1%. Or maybe I just have better things to do than constantly watch my phone's charge...not a major issue, after using my 13 pro max for a bit, then putting it down, it'll drop by 2-3% every now and then instead of going down by 1%, most likely a visual bug
who said I was constantly watching my phone, so it's normal to come back 30 seconds later and see a 3% drop, don't think so.What makes you think it should drop by 1%? I don't think I've ever had a mobile phone that consistently drops by 1%. Or maybe I just have better things to do than constantly watch my phone's charge...
Weird! So if someone’s trying to setup their new iPhone this morning, they’re either stuck on an earlier build or can’t activate?Apple stopped signing iOS 15 for iPhone 13 series so possible a new build is coming
Exactly. Seems a little premature. Usually they will stop signing once the update is out at least.Weird! So if someone’s trying to setup their new iPhone this morning, they’re either stuck on an earlier build or can’t activate?
Stuck with the earlier build (19A341) the iPhone came with.Weird! So if someone’s trying to setup their new iPhone this morning, they’re either stuck on an earlier build or can’t activate?
But the earlier build had issues, too, right? Like the Apple Music bug and the "Apple Watch not connecting" Bug? Does this mean Apple is saying that the issues on the earlier build weren't as bad as the newest build?Stuck with the earlier build (19A341) the iPhone came with.
Yes you are correct about the music bug.. but 19A346 is fine if you do it through the IPSW not OTA something about the OTA breaks things.. I restored my phone through IPSW and have no issues it actually fixed the storage bug tooBut the earlier build had issues, too, right? Like the Apple Music bug and the "Apple Watch not connecting" Bug? Does this mean Apple is saying that the issues on the earlier build weren't as bad as the newest build?
But if build 19A346 is no longer being signed for the iPhones 13, and it comes with build 19A344, you're stuck with the Apple Music Bug and the Apple watch connection issue. You or I may have no problems downloading an IPSW and whatnot.. But I guarantee you we're in the minority with that.Yes you are correct about the music bug.. but 19A346 is fine if you do it through the IPSW not OTA something about the OTA breaks things.. I restored my phone through IPSW and have no issues it actually fixed the storage bug too
you are absolutely correct.. and it is very odd that Apple did this without another option for iPhone 13 users .. there is someone now that is on 15.1 beta 1 thread and is having carplay issues, he can’t go to beta 2 because there is no public release and he cant go backwards to 15.. I just told him he is kinda screwed till later today what Apple is going to do..But if build 19A346 is no longer being signed for the iPhones 13, and it comes with build 19A344, you're stuck with the Apple Music Bug and the Apple watch connection issue. You or I may have no problems downloading an IPSW and whatnot.. But I guarantee you we're in the minority with that.
Well, from what I can remember that person should still be able to press Option + Check for Updates in Finder and then manually navigate to iOS 15.1 beta 1 (if they still have that IPSW) and install it over b2. May be helpful, but they’d need that file.you are absolutely correct.. and it is very odd that Apple did this without another option for iPhone 13 users .. there is someone now that is on 15.1 thread and is having carplay issues, he can’t go to beta 2 because there is no public release and he cant go backwards to 15.. I just told him he is kinda screwed till later today what Apple is going to do..
He is on beta 1 , sadlyWell, from what I can remember that person should still be able to press Option + Check for Updates in Finder and then manually navigate to iOS 15.1 beta 1 (if they still have that IPSW) and install it over b2. May be helpful, but they’d need that file.
Oh! I’m sorry, I misread that as them being on b2 and needing to go back to b1..He is on beta 1 , sadly
it does not make sense, because apple always signs a few days after the release of a new version the old one, in case there are serious errors.Weird! So if someone’s trying to setup their new iPhone this morning, they’re either stuck on an earlier build or can’t activate?
Makes me wonder if 15.0.1 was meant to come out Monday, but got delayed, and they didn’t stop the automation for the disabling of signing for 15.0……it does not make sense, because apple always signs a few days after the release of a new version the old one, in case there are serious errors.
The earlier build on the 13’s also predates the Pegasus Exploit fix, which is more of a concern.But the earlier build had issues, too, right? Like the Apple Music bug and the "Apple Watch not connecting" Bug? Does this mean Apple is saying that the issues on the earlier build weren't as bad as the newest build?
Normally old versions of ios are signed a week after releasing a new version, it makes no sense to stop signing a version even before releasing a new one.Makes me wonder if 15.0.1 was meant to come out Monday, but got delayed, and they didn’t stop the automation for the disabling of signing for 15.0……
Maybe it was meant to be out before Monday then. Either way, I think maybe it’s an automation that’s not been disabled.Normally old versions of ios are signed a week after releasing a new version, it makes no sense to stop signing a version even before releasing a new one.
Something tells me if they wanted to start signing 19A346 again due to an error, they'd have done so by now. Strongly suspect 15.0.1.Haha, what a disaster. They will have to release 15.0.1 today, or start signing 19A346 again.