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.
Knowing that AirPods Max 2 pre-orders open next Wednesday with an estimated delivery a week later, we'll see the RC next week with an official launch the week of March 30th...
 
  • Like
Reactions: Kal Madda
I’m hoping that background security improvements will lead to shorter beta cycles, since most iOS updates are primarily security fixes anyway.

But also, I’m predicting this will lead to less frequent iOS updates. If security fixes can be pushed out separately, there’s less of a reason to do an iOS x.5 or whatever.
 
I would anticipate a beta / RC yet this week. Unless the latest beta is patched for the security release from today, I would think Apple will want to get an update out for the beta branch as well. I know it’s a test software, but I can’t see Apple wanting to chance it.
Agreed. The beta branch will soon see an update to patch the vulnerability.
 
Erm, why wouldn’t they just release a security response instead if that were their impetus 🙂

My speculation is that if it was being released, it would have come same time as the version yesterday. Security usually isn't one of those things where updates get held back if the incident is big enough. However since it wasn't, I could see one of the following:

1. We see it today and the release was held back to get the general population patched first. Beta testers are a much smaller population in the overall grand scheme.
2. It wasn't worth their time since they could just incorporate it into the next beta / RC and release this.
 
My speculation is that if it was being released, it would have come same time as the version yesterday. Security usually isn't one of those things where updates get held back if the incident is big enough. However since it wasn't, I could see one of the following:

1. We see it today and the release was held back to get the general population patched first. Beta testers are a much smaller population in the overall grand scheme.
2. It wasn't worth their time since they could just incorporate it into the next beta / RC and release this.
I'd think they clearly found some kind of system issue that needed to be addressed sooner than later.. Whenever we do end up seeing the RC, there's still roughly a week or so after until it's officially out. Clearly there was an issue that needed to be addressed before then.
 
  • Like
Reactions: NBKindaGirl
My speculation is that if it was being released, it would have come same time as the version yesterday. Security usually isn't one of those things where updates get held back if the incident is big enough. However since it wasn't, I could see one of the following:

1. We see it today and the release was held back to get the general population patched first. Beta testers are a much smaller population in the overall grand scheme.
2. It wasn't worth their time since they could just incorporate it into the next beta / RC and release this.
#1 : It’s a security patch. They test it thoroughly before the public release not after.
#2 : Unless it’s being actively exploited in the wild including the betas, the fixes come in the subsequent betas.
 
Most random update ever

IMO, that update failed, epically. Firstly, unless somebody was told there were an update and where to find it exactly, people would not know where to look for it and the OS would not notify them. I have had an iPad with automatic updates enabled plugged into a charger and connected to WiFi overnight and nothing happened. So what’s the point of these background security updates, when we need to proactively initiate them and then our devices would restart, which is exactly the same amount of effort as initiating the “regular” OS updates? 🤷🏻‍♂️
 
  • Haha
Reactions: UpsideDownEclair
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.