iOS 8.0.1 released, broken on iPhone 6 models, withdrawn
sixcolors.com
sixcolors.com
Experiencing some small scale analogs to this is what taught me to really appreciate the sort of simple, manual rigor that I often see from (much) older engineers.
That's not to say that such things weren't done here - who knows. It's more a thought on what I sometimes perceive to be over dependence / confidence in automated testing.
Now...
Is there a term for the sort of "If X was Y then..." conjecture we have dotting this thread?
Here, in relation to Apple it's "If Steve Jobs was alive...". In boxing it was "If Cus D'Amato was alive..."
Instructions: https://gist.github.com/locriani/f0f5f4f71a28945c3750
[1] http://9to5mac.com/2014/09/24/apple-ios-8-downgrade-instruct...
The only times I have violated this rule was when somthing was already so broken that a new version would still be considered an improvement even with warts.
Just one of those more conservative engineers.
Also, there's a huge, HUGE, difference between critical well-vetted security updates and a whole host of other updates that have no material value and can potentially cost you a bundle.
I'll give you an even more extreme example: Some of our engineering workstations are still running Vista. Why? Because upgrading to 7 or 8 offers nothing of value and will trigger a few weeks of upgrading major applications and software dependencies. We will finally be forced to make the update this year because Solidwork, Solidworks FEA Simulation, the associated CAM and other software require 7 as a minimum. We are far more likely to build new machines from scratch than to upgrade the existing machines. Part of the reasoning is backup during the transition.
Just happened to a friend, she can't install the update she had downloaded.
Problem is, if you were quick on the draw and updated as soon as it came out, there's no ipsw for the iPhone 6/+ on the dev center. Though the solution is to restore to last known good, LKG is not available through the usual channels.
My heart goes out to those unknown folks at Apple who are now having a really bad day. I doubt we'll get it, but I'd love to read a post-mortem of this event. I suspect it'd be educational, as I have a hard time imagining how an org like Apple could ship a release this obviously broken.
Caveat: I have not tested these myself, nor has anyone on my team. We are holding off until we deem it necessary to get the devices working again (an enthusiastic tester who was quick on the draw this morning managed to hose our only two iPhone 6 devices.)
I wonder what I do with my now-eternally-updating iPhone.
Crashing often now (buggy iOS 8)
Bent (bentghazi)
Broken because of this
Thank god we aren't using --gate or --geddon for this one.
Would be interesting to hear what carrier it broke on for people.
People underestimate how hard it can be to catch problems that only manifest on a particular network setup, etc., even with a formal test team.
As another commenter said, I'd love to see a post morteum strictly in the interests of "don't let this happen to you". Sadly, we're unlikely to ever see it.
1: https://news.ycombinator.com/item?id=2661209 2: https://github.com/MrMEEE/bumblebee-Old-and-abbandoned/commi...
Whenever I see a sentence like this I usually write it off to hyperbole, but my experience with iOS 8 has been similar to yours.
If you hook up to iTunes, you can use it to do just the OS update... sync is optional.
I had to turn iMessage off and back on again in order for Apple to re-register my number... until then I was unable to send to any existing contacts.
What a terrible position to put your customers and retail employees in.
I'm guessing Apple isn't going to throw a bone to people who won't update their phones. I doubt they'll help the iPhone 4 users, but that would be nice.
Edit: would this disclosure be the responsibility of Apple or the wireless carrier? Apple may not have contact info for the customer, which would mean carriers worldwide need to notify customers of the risk to their personal data (e.g. financial passwords), as soon as they open a web site or an app that displays network-origin data, e.g. an email with an image.