It would if the build number is higher.because ota doesn't work for re-release if you are already on an older build of 17.6.1
but it works if you plug into computer.
It would if the build number is higher.because ota doesn't work for re-release if you are already on an older build of 17.6.1
but it works if you plug into computer.
Is it confusion or incompetence?My god the confusion in this company is unbelievable.
that's how betas work. higher and higher builds even for same version number usually work ok for otaIt would if the build number is higher.
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.Love how people assume that updates might fix all sort of issues even when Apple says the fix targeted for one bug.
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.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
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:Doesn’t seem to be relevant for most iPhones. Xs and Xr models seem to receive the overhauled version.
Perhaps different time zones and locations .well i already updated 2 iphones and am now in the process of updating an ipad and it's still working, so I don't think it got pulled.
Why would it still be working if it got pulled?
screen shot of progress literally 3 seconds ago:
View attachment 2407514
I had the same issue. I took a screenshot...Release notes via Finder when I plugged in an iPad mini 6 to my Mac said it fixes an issue with Fitness+.
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.Why would they not call it 17.6.2? This is so stupid
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.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…
Unfortunately for things like this very few read or listen. Complaining is easier than reading and inquiring.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.
I was trying to be nice. The latter, sure enough.Is it confusion or incompetence?
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.Unfortunately for things like this very few read or listen. Complaining is easier than reading and inquiring.
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