Yep. Part of how they did it is that a previous minor release included a dry run, where the OS would try the conversion, collect diagnostics, then undo it.
All users really noticed about that was an unusually slow upgrade.
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.
Apple's Craig Federighi Explains Why iOS Auto-Updates Often Arrive Several Weeks Late
- Thread starter MacRumors
- Start date
- Sort by reaction score
Yep. Part of how they did it is that a previous minor release included a dry run, where the OS would try the conversion, collect diagnostics, then undo it.
All users really noticed about that was an unusually slow upgrade.
I’ve set my Auto Update to off but not so I can download it sooner but so I can download when I want to. I usually wait a while and see if there are problems with any new release and if so I don’t download until they have been fixed.
Currently there is a reported iPhone 13 battery problem with IOS 15.0 and until I hear that either the problem really doesn’t exist or that it’s been solved I’m not downloading.
Currently there is a reported iPhone 13 battery problem with IOS 15.0 and until I hear that either the problem really doesn’t exist or that it’s been solved I’m not downloading.
I have auto updates turned on.. why do I have to keep telling it ... yes, install now... and put my passcode in, etc.... I'm explicit telling it ... and I still have to intervene multiple times...
hopefully with a redesigned mac mini, macbook air, mac pro, and maybe even imac pro, people will focus more on these new machines than the operating system itself in the 2022-2023 macOS. this way, they can do no new feature upgrades with monterey and use this time solely to fix macOS
Auto update actually NEVER happens on any of my apple tv's. I have auto update on, and mine are all still running 3 point versions behind. I always have to manually trigger those if I want the latest.
I prefer letting others test the "brickability" of a new release for both iOS and macOS.
I got a hard kernel panic when trying to initiate sidecar on macOS 12.3. I was getting hard kernel panics in 12.2.1 and 12.3 beta when waking from sleep with a TS4 attached. Apple makes great hardware but macOS needs to be debugged.
Always kind of presumed this was the case, I remember the days when new updates would take hours to download because of the immediate demand, then Apple started rolling out update availability to mitigate the issue; this seems like the logical next step, short of spending massively to increase server capacity just for the few times a year Apple releases a major update. I do hope they have an altered procedure when updating immediately is imperative, such as when a security flaw is reported.
I'll agree that software quality has been down in recent years. I'm not sure if that says much about Federighi, Forstall, or Serlet, though. The user base has grown more than tenfold compared to Forstall and Serlet. Overall complexity is way up.
Grammarly can’t even attempt to make sense of this run- on, so I don’t know why you’re using this to judge someone’s reading comprehension, lol.
Uhhh, no? I don’t think there could be an argument for this at any point in time, ever. You do understand resources are finite, right?
Staggered update rollouts are common and smart. If any issues arise with the early upgrades (which can absolutely happen), they can pause the rollout and make the fix before too many people are affected.
I just leave auto update on and I get updated when it’s my turn. I have work to do and no time for problems. I don’t mind waiting.
I just leave auto update on and I get updated when it’s my turn. I have work to do and no time for problems. I don’t mind waiting.
No, it's not. Bugs are only part of the equation. Apple is also looking at how the general public accepts an update. There are updates that introduce functionality that pass all quality standards, that are accepted by beta users (who have different pyschographics than the average user), but end up being rejected by the public at large. By the time that Apple makes a public release, they have general confidence that the fruit is ripe. Apple can only pass out so much fruit at a time in an orderly fashion (server capacity)... and if it helps prevent rotten spots (bugs) while at the same time ensuring everyone enjoys the flavor (changes and additions to functionality) they aren't crossing their fingers and hoping for luck. They are using a strategy that helps with quality control and satisfaction. It's not a 2nd beta test.
This doesn’t explain why the devices ask constantly if you would like to update that evening, only to fail to update. This has happened to me multiple times on many devices.
Last edited:
Still waiting for iOS 14 updates Craig
Isn't iOS 14 finished? I could be wrong and also I don't feel like looking it up but I thought I read that iOS 14 was done getting updates.
About app updates: on App Store Connect, developers can choose to intentionally delay rollout for all users by up to 7 days. The delay is then automatically managed by Apple. The decision is completely up to the developer, but I know many developers that choose this option (most developers who have many users).