Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It would if the build number is higher.
that's how betas work. higher and higher builds even for same version number usually work ok for ota

but not in this case.

this one is a re-release and many people attempting ota are not seeing it because it is the same version number.

i get why sometimes apple may pull and re-release within a few hours, but not 12 days later.

clearly it should have been version 17.6.2 not a re-release of 17.6.1 with higher build
 
  • Like
Reactions: JapanApple
Love how people assume that updates might fix all sort of issues even when Apple says the fix targeted for one bug.
Software is complex and unpredictable. If it's just battery issues then you might actually get lucky even when the fix is for a diff issue.
 
that's how betas work. higher and higher builds even for same version number usually work ok for ota

but not in this case.

this one is a re-release and many people attempting ota are not seeing it because it is the same version number.

i get why sometimes apple may pull and re-release within a few hours, but not 12 days later.

clearly it should have been version 17.6.2 not a re-release of 17.6.1 with higher build
This happens often with beta builds. They re-release the same beta with diff build number and it gets pushed for everyone on the prior versions.
Now if there's another explanation for why this didn't get pushed I don't know but I'm fairly positive that they don't just go by version#. Build# is a proper way of version tracking since it's unique.
 
Doesn’t seem to be relevant for most iPhones. Xs and Xr models seem to receive the overhauled version.
I wasn't offered it on XR (already on 17.6.1) but when attached to iTunes (and on Mac finder) was then was offered the update. The release notes state one line:

"This update fixes an issue that may prevent access to Apple Fitness+."
 
Last edited:
I think a lot of eyes will be on tomorrow do they release 17.6.1 OTA, 17.6.2 or this is it and neither at all
 
Release notes via Finder when I plugged in an iPad mini 6 to my Mac said it fixes an issue with Fitness+.
I had the same issue. I took a screenshot...

Screenshot 2024-08-19 at 6.21.37 PM.png
 
  • Like
Reactions: VineRider
Does anyone know why this would appear? How can I find out what “purchased items” the dialog is referencing?
Screenshot 2024-08-19 at 5.46.30 PM.png
 
Last edited:
I updated my iPhone 15 Pro Max via Finder and it took like 6 minutes to download the 8GB update file. What really took forever was backing up my iPhone…
 
Why would they not call it 17.6.2? This is so stupid
Iterating the version triggers certain implications as far as adoption. In some environments, any iteration to the version number could trigger internal policy that requires a certification process for adoption, potentially delaying the installation by weeks or months. By keeping the version number the same, it is automatically deployed in any environment that has already approved 17.6.1.
 
I updated my iPhone 15 Pro Max via Finder and it took like 6 minutes to download the 8GB update file. What really took forever was backing up my iPhone…
If one can’t update via their phone then this update is worthless to most. Apple removed many of the features that one could do via iTunes in the past when the phone was connected.
 
For everyone wondering how to update when not seeing the OTA update and not having a Windows PC:
Connect your iPhone to your Mac, go to Finder and there click on your iPhone, update, and you‘ll be surprised.
 
For everyone wondering how to update when not seeing the OTA update and not having a Windows PC:
Connect your iPhone to your Mac, go to Finder and there click on your iPhone, update, and you‘ll be surprised.
Unfortunately for things like this very few read or listen. Complaining is easier than reading and inquiring.
 
Is it confusion or incompetence?
I was trying to be nice. The latter, sure enough.
I’ve been trashing their software department at every chance I get.
They are a joke. The amount of issues I’m experiencing daily on my MacBook Air is just unbelievable.
There is a glitch in every feature you try to use. They are good at surfing the web nowadays, that’s about it.
Try do do anything outside of safari and good luck.

For a year, apps couldn’t be opened after switching between user accounts. I have reported the issue 20 times and ultimately got fed I’m and emailed one of the senior VP directly. It took them another 5 months to patch it.

Not to mention continuity and handoff not working, also after a user account switch. Another issue that has been there for a good 7 years now.

With the risk of sounding cliche I must say: how much I miss Steve.
 
  • Like
Reactions: Harry Haller
Unfortunately for things like this very few read or listen. Complaining is easier than reading and inquiring.
Except that a friend of mine did it the other day with a brand new iPhone and it resulted in a corrupt firmware. Another example of how they lost their head.
 
Apple have done this in the past... They released a public update then re-released the same version update with a different build number...

iOS 10.1.1 [14B100] - October 31 2016
iOS 10.1.1 [14B150] - November 09 2016

iOS 12.1.2 [16C101] - December 17 2018
iOS 12.1.2 [16C104] - December 20 2018
 
Just updated an iPad that I rarely use to the first version of that update 1 or 2 days ago. Same for an iPhone 8 Plus that also got such an update for iOS 16. Is there another one too for iOS 16?

Those small .x updates took both very much longer than installing new beta versions of iOS 18.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.