Apple has released iOS 8.0.2. It’s available now via Settings > General > Update or over Lightning to USB tether to iTunes on your Mac or PC. This comes just one day after the iOS 8.0.1 update left iPhone 6 and iPhone 6 Plus customers unable to use Touch ID or connect to cellular networks. Apple promised a fix within days and delivered it with a day.
Quick response by Apple.
to wait a few days before installing let the others test it
Indeed
But no less a screwup.
And there is the reason why many Android manufacturers would rather not issue updates to phones. Testing is hard, and testing on dozens of older models even harder. I think this situation should improve as phones settle on more standard components and drivers stabilize though.
What do older models have to do with this? This affected Apple’s very latest and, quick response or not, there is no excuse. Had it affected a certain obscure model of 4S I would understand, and your argument would apply here, but it wasn’t some obscure old model. It was the very devices many materialistic hipsters shelled out a shit ton of money to get, and were then broken within days. Pathetic no matter how the Apple fans try to dress it up, and there would have been no difficulty in testing. Pure sloppiness.
In your perfect world, there is no excuse for a mistake, ever. However in the real world, shit happens.
I think how you deal with a situation is often as important as avoiding the situation in the first place.
I think people get it. Apple messed up. The person you replied to seems to get it as well, judging from his first sentence.
You missed the point by a mile.
First of all I said that it was a screwup quick response or not, so I’m not making excuses for anyone. The point is that testing updates with all configurations is not easy or even feasible, so it is understandable that Android manufacturers are reluctant to issue updates to avoid exactly this situation. The only sure way not to run into problems with an update is not to do the update.
Alright stop hyperventilating. This is definitely a screwup like I already said, but also engineering reality. By the way, 40,000 iPhone 6s were affected by this bug, or about 0.4% of the units sold. That’s bad, but not like every iPhone 6 out there was broken.
Edited 2014-09-26 21:12 UTC
leos,
Apple pulled the update after only one hour, so the likely explanation is that only 0.4% had time to install it. If they had not removed the update, the damages could have affected a great deal more.
I think you underestimate the average American Apple Fan’s rate of updating. They’re much more apt to install them quickly than the Windows croud, especially if their new device is still shiny.
Testing older models is no more difficult than testing new models. But, testing costs money and spending money is what most companies try to avoid doing.
There’s nothing that points to the problem having to do with `non-standard components` or `driver instability`. Simple negligence is the culprit here. Give this a read:
http://www.bloomberg.com/news/2014-09-25/apple-s-iphone-software-sn…
Spoken like someone who never did any testing Testing is not only expensive, it is also very difficult with a product that has literally millions of different configurations of hardware and software.
So some unsubstantiated rumour is somehow more convincing than basic engineering principles? Sure.
Yes, that’s true but you do realize we’re talking specifically about the iphone right? Are you suggesting there are `literally millions of different configurations of hardware and software` regarding a stock Apple iphone? If yes, please cite your source. If not, why are you bringing something up knowing that it doesn’t apply to the subject?
Bloomberg is a credible source but that aside, you oppose the idea that the cause of this problem isn’t “non-standard components” or “driver instability”. So, please provide a citation that lends any evidence what-so-ever that it _is_ caused by either of those. Further, how “engineering principles” has anything to do with the problem, or what `basic engineering principle` you think has been violated.
Millions? Let’s see, this OS version supports the following devices: iPhone 4S, 5/5C, 5S, 6, 6 Plus, iPod Touch (5th generation only), iPad 2, 3, 4, iPad Air, iPad Mini 1, 2.
So that’s a grand total of 12 products, make it 23 to adjust for the GSM/CDMA markets. Storage options are irrelevant for this type of testing.
I’m fascinated as to how exactly you can confuse a “couple of dozen” with “millions.” In fact that is one of the defining characteristics of Apple’s business model: extremely limited (in number) & simplified product lines for agile SKU management. So perhaps it is you the one who could be projecting their lack of understanding on the realities of testing.
Edited 2014-09-28 20:16 UTC
Apple doesn’t have an issue of testing on dozens of older models when it comes to their mobile platform. They support a few models of iOS devices with this latest update, and that’s why people expect it to work well. Closed ecosystem, and not having everyone and their brother making an iOS device. Testing is hard. That’s why Apple had an extensive beta. I believe this was really just a product of poor quality control, and poor project management.
I have installed the new update and all is working well. You can now safely update your iPhone 6/6 Plus…:-)
poor QC. Their OS, their own hardware. In this age, it cannot get any better for testers. Overall very sloppy job by Apple. Phones bending, iOS crashes and bugs – what a mess. I think they rushed to the market.It could be partly blamed on outsourced manufacturing. Any innovative ideas are quickly leaked to competitors who have more rapid manufacturing processes and facilities.
Regading iPhone bending: Consumer Reports corrects the lies @ http://consumerist.com/2014/09/26/consumer-reports-test-shows-it-ta…
My biggest gripe with 8 was that my wifi would just randomly drop and no networks could be found. Only a reboot would fix. After 8.02, the wifi has been rock solid. It seems like everything is as it should be so far…