Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I hope they don’t can 26.0.2 after testing it internally, it would be unprecedented behavior for them and I am more interested in installing that than 26.1
I just went back through this thread to see if I could find some indication as to why you're so upset right now, and couldn't find it. Can you please enlighten us as to why you're so dead set on hating 26.1?
 
There is no truth in Apple releasing an update that hasn't't been released yet 😆 And telling people how unstable it is when it's not unstable, is in my mind fear mongering. Plus, if there IS any testing being done internally with 26.0.2, any "bug fixes" you'll be wanting would be included in 26.1
It’s been particularly unstable for me, even more so than when I was on any of the iOS 26 betas. If that’s fear mongering, I’d rather be fear mongering than ignorant, which would be the case if I said everything is fine when it clearly is not.

Even if the same (or any) bug fixes are implemented in 26.1, rolling out a new build that they’ve clearly already developed and have been testing would be pretty simple and the correct course of action instead of just throwing hands to the wind and saying “ahhh screw em, let them wait another 2 weeks”


Fear mongering would be me speculating that the release of 26.0.2 was canceled because they discovered some severe device bricking bug in their code that they couldn’t let out in good conscience. Such a catastrophe wouldn’t be unheard of for Apple… what would be unheard of is them pulling it rather than letting out flawed software to the masses and letting everyone else sort it out! See: the versions of Apple Devices that were destroying iOS and iPadOS installations for MONTHS before they were patched

Of course this was never officially documented and Apple even kept encouraging customers to download and use the broken software. It would only be through reading the MacRumors forums, or through personal guinea pig testing (as I did myself) that anyone could know the software would seriously screw up their device if used as advertised or intended.

Maybe some rogue apple developer implemented a backdoor in 26.0.2 with significant security implications, like a botnet or worm that views everyone’s iMessages. It’s a good thing they caught this before, god forbid, they may have released such a thing. It’s no wonder they canceled this update. Ahh. I’ll stop fear mongering now.

I just went back through this thread to see if I could find some indication as to why you're so upset right now, and couldn't find it. Can you please enlighten us as to why you're so dead set on hating 26.1?

It’s pretty much right there in the post you quoted, I am just more interested in 26.0.2. But only the golden few at Apple are worthy of access to such precious IPSWs. It was never meant for us.
 
It’s been particularly unstable for me, even more so than when I was on any of the iOS 26 betas. If that’s fear mongering, I’d rather be fear mongering than ignorant, which would be the case if I said everything is fine when it clearly is not.

Even if the same (or any) bug fixes are implemented in 26.1, rolling out a new build that they’ve clearly already developed and have been testing would be pretty simple and the correct course of action instead of just throwing hands to the wind and saying “ahhh screw em, let them wait another 2 weeks”


Fear mongering would be me speculating that the release of 26.0.2 was canceled because they discovered some severe device bricking bug in their code that they couldn’t let out in good conscience. Such a catastrophe wouldn’t be unheard of for Apple… what would be unheard of is them pulling it rather than letting out flawed software to the masses and letting everyone else sort it out! See: the versions of Apple Devices that were destroying iOS and iPadOS installations for MONTHS before they were patched

Of course this was never officially documented and Apple even kept encouraging customers to download and use the broken software. It would only be through reading the MacRumors forums, or through personal guinea pig testing (as I did myself) that anyone could know the software would seriously screw up their device if used as advertised or intended.

Maybe some rogue apple developer implemented a backdoor in 26.0.2 with significant security implications, like a botnet or worm that views everyone’s iMessages. It’s a good thing they caught this before, god forbid, they may have released such a thing. It’s no wonder they canceled this update. Ahh. I’ll stop fear mongering now.



It’s pretty much right there in the post you quoted, I am just more interested in 26.0.2. But only the golden few at Apple are worthy of access to such precious IPSWs. It was never meant for us.
You keep throwing out buzzwords like “unstable” but I still don’t think you’ve made a post explaining what is actually “unstable.” A respring or crash is hardly “unstable”. By that logic every single OS is unstable.

Please tell us what is so broken on iOS 26.0.1 that you believe 26.0.2 would actually fix? Sounds like iOS 26.1 has barely fixed the graphic bugs of 26.0.1 so I have a hard time believing that whatever is so unstable on your device would be fixed in a .0.2 update if there are still issues in 26.1 B4.
 
You keep throwing out buzzwords like “unstable” but I still don’t think you’ve made a post explaining what is actually “unstable.” A respring or crash is hardly “unstable”. By that logic every single OS is unstable.

Please tell us what is so broken on iOS 26.0.1 that you believe 26.0.2 would actually fix? Sounds like iOS 26.1 has barely fixed the graphic bugs of 26.0.1 so I have a hard time believing that whatever is so unstable on your device would be fixed in a .0.2 update if there are still issues in 26.1 B4.
An operating system that completely crumbles multiple times under the weight of being simply interacted with, is unstable. It’s not asking too much for this to not be the case.
If ios crashed once a month it would be a problem, 3 times is excessive. I can very confidently call this a relatively unstable version of iOS, based on my history of using iOS devices daily for almost 20 years at this point.

If you step in something that looks like ****, smells like ****, and feels like ****, must you taste it as well? or are 3 senses enough to call it what it is?


An update doesn’t necessarily have to include bug fixes for bugs to be fixed. Sometimes the simple act of installing an update by itself can resolve small issues that just “happen” from the natural entropy of just using a computer system. So I would be happy to install an update for that reason, but it’s an update that Apple seems to be pulling, and people here seem to be applauding for some reason. You can’t install an update that does not exist.


All I stated is that I wished it would come out and I’m disappointed in the cancellation, and this has led to all this dogpiling and odd justification of the situation. Really strange hivemind behavior.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.