Have you tried reinstalling 26.0.1 via IPSW over your existing installation? I’ve seen people mention that doing this has sorted issues they’ve had. Have never tried myself, but could be worth a try for you.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS 26 Speculation Thread
- Thread starter Kylo83
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
just got a song title slipping into my my mind reading this ... sorry couldn't resist ...
I have a feeling that next week is when we’ll get new drops.
Next Monday/Tuesday - 26.0.2 and 26.1 RC.
Altho it’s weird to release 26.0.2 and within a week release 26.1.
Wondering if they’ll just skip 26.0.2 altogether and just do 26.1.
Haven’t attempted this, forgot it was possible actually! but may give it a try. In all honesty if I’m going to take the time to “update” I’d rather do it for an actual update, but I suppose it is an option.
"I don't like X because I prefer Y," is not any kind of clear justification. So to be more direct: why don't you just update to 26.1 when it drops? What are your actual reasons for suggesting that you might refuse that update, specifically?
I ask because, in stark contrast with your experience on 26.0.1, I haven't observed any meaningful issues with 26.1 b4.
While I am not going to make a case for @MrRom92, as he has been the most vocal about the issues he has experienced, I will say that I have seen iOS operate very differently across three different devices. My company-supplied phone has very few apps. I use it mostly for email, MFA, and a few other things. I have only a few apps loaded on it. That phone has excellent battery life, no issues with resprings or even redraws of icons. My personal phone, which has a dual SIM, a TON of apps loaded on it, and which I use most throughout the day, has seen redraws, messaging issues, keyboard lag, and a few others. No resprings. My iPad acts much like my company phone—except it, too, has a lot of apps, a lot more downloaded content, and is set up similarly to my personal phone—but no redraws, resprings, etc.
My point is, we all use our phones differently, with differences in which apps we use, how many, and all of that, and despite what some may say or argue, this impacts how the phone behaves. I do not blame iOS for all of these issues. I think some of this is caused by the apps we install. Don't tell me I am wrong - show me. Prove that this is not possible and maybe I will think differently, but with three different Apple devices all running the same software but different results, its hard to believe that something in there does not affect how our devices act.
My point is, we all use our phones differently, with differences in which apps we use, how many, and all of that, and despite what some may say or argue, this impacts how the phone behaves. I do not blame iOS for all of these issues. I think some of this is caused by the apps we install. Don't tell me I am wrong - show me. Prove that this is not possible and maybe I will think differently, but with three different Apple devices all running the same software but different results, its hard to believe that something in there does not affect how our devices act.
I gotta agree that it isn't looking like this will be released. I can count on one hand the times we heard of an update and it didn't come.
I'm thinking MacRumors jumped the gun here. They are the ones that published the story, and all other news sites picked it up and cite/point back to MacRumors. Unlike with 26.0.1, I haven't seen any other sources being able to corroborate the story with further proof.
I'm curious if MacRumors is still seeing evidence of 26.0.2 in their logs. Perhaps they should do some more investigation and own up to their "goof" if they aren't seeing anything anymore.
For all we know, it could have just been some employees testing a local/personal build. Or maybe it was intended to be the day one update for the new devices that came out yesterday, but then ended up deciding to go with an updated build of 26.0.1 instead. It would be funny if it was just a group of people/employees that spoofed their user agent string to make it look like they were running 26.0.2 as a prank.
I concur, I suspect the re-release of 26.0.1 for those particular devices was initially meant to be and tested as 26.0.2 then they decided to just make a new 26.0.1 build for those day one releases to keep things in sync version wise.
It takes less than 5 minutes to install once it’s downloaded. I just did that with 26.1 b4 just because I was bored yesterday.
And I can assure you, 26.0.1 is a real update, not fictional.
lol
On no planet does any version of iOS take less than 5 minutes to install
Another respring this morning, by the way. Because I dared to swipe down and open the Notification Center. Super stable, no problems here!
Are we really going to go down the installation time rabbit hole again?
On no planet does any version of iOS take less than 5 minutes to install
Another respring this morning, by the way. Because I dared to swipe down and open the Notification Center. Super stable, no problems here!
I updated my iPhone 16 Pro Max and my 2018 iPad Pro both in roughly 6-7 minutes. I'm sure, individually, each one was each updated in under 5 minutes, but I'm saying BOTH devices updated and were back at the Home Screen in roughly 7 or so minutes.
The last time I had a respring was in the early iOS 26 betas.. And just to clarify, because I thought it was less, but I've currently got 662 (!) apps installed right now, too. I would take your phone to an Apple Store and tell them these issues you're having so they can help you figure this out. If all of the issues you're having were baked into iOS, we'd all be having these issues, and we're not :-/
I said the actual installation time which doesn’t include “preparing to install” part. It doesn’t take much longer than 5-10 mins. If you’d like me to be more specific, I can get you one on Monday.
No one’s doubting you’re having issues. But from what I gathered from your previous posts, you probably have a corrupt config and would benefit from a fresh install. It’s a PITA but you don’t have to worry about that again for years. I’d suggest waiting until 26.1 RC or public is released to do that though. But if you’re still waiting on Apple Devices though, I’ll keep praying for you.
On the good news front, I would venture to guess Monday or Tuesday for 26.1 RC. I almost wonder if the A build might just go public next week if they want to stick with the trend schedule. But I think this might be like a 2% chance and we get the RC next week. So we are probably looking at Nov 3rd for public since Apple likes Monday releases.
Last edited by a moderator:
This sounds good to me. Beta 4 is feeling good, an RC with some extra polish would make it a fantastic release.
im wondering if they would just release iOS 26.1 next week
going all the way back to iOS 18.1 the releases have been the last week of october.. there hasnt been any in november.
going all the way back to iOS 18.1 the releases have been the last week of october.. there hasnt been any in november.
Unlikely, unless we have a very short RC schedule. Every .X update has had an RC since iOS 14.2, with the shortest being 5 days.
Officially labeling a particular build as a "release candidate" has always seemed like an odd practice to me. Realistically every build is a release candidate until the bug reports start flooding in... and declaring an RC build doesn't even mean that an RC2 won't drop the following week instead of a final, like last year with 18.2. So why bother with an RC at all? Just keep calling them betas until the decision to actually release that "final" version is made.
And honestly it seems like it’s been a long time since the “RC” build has been the true build released the following week—either an “RC2” follows it or the publicly-available final release ends up being a different build number. May as well just be “beta X” until the final one drops.
I would disagree that every build is a potential RC, because betas 1-4 (for 26.1) have beta logging and the build number alone tells you its not a release candidate.
Technically speaking, the RC is the final beta, just without the beta files enabled. RC does not contain the build letter. By calling it an RC, Apple can test the final build without beta enabled logging to make sure there are not catastrophic issues requiring a potential RC2.
I think a release candidate is just a "heads up developers, be ready to update new builds of your apps"