I'm surprised it didn't go to developers first. I think somebody put it on the wrong system and once it was done there was no going back. We always hear about the updates when they hit the developers. This was direct.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Says iOS 8.0.2 Update is in the Works, Directs Users to Reinstall iOS 8
- Thread starter MacRumors
- Start date
- Sort by reaction score
I'm surprised it didn't go to developers first. I think somebody put it on the wrong system and once it was done there was no going back. We always hear about the updates when they hit the developers. This was direct.
No that's is one of the updates in the release notes. "Fixes an issue that could cause unexpected cellular data usage"
So if they turn off cellular service that takes care of it
Absolutely. Fast tracking means proper testing did not occur. Also, its is clear that 8.0.1 had some late stage bug fixes added to it.....bug fixes that were NOT present in 8.0.1 when it was seeded to carrier partners for testing 3 full weeks ago.
Even in my own company, if a build is ready to go, and dev decides to add another bug fix, we delay the push, until it is tested and verified.
It can be infuriating when you just want to get an update out to users....but it is better than issuing something that might be broken.
I'm astounded after reading hundreds of posts in Apple-related forums of people actually thanking Apple for their "quick" response. Have things really gotten this bad in Planet Fanboy?
Nevermind that they ignore the fact that this slipped by Apple's entire organization, including their engineers, programmers and QA/QC departments. Does nobody at Apple have an active iPhone with a cell connection and/or Touch ID enabled?
Nevermind that they ignore the fact that this slipped by Apple's entire organization, including their engineers, programmers and QA/QC departments. Does nobody at Apple have an active iPhone with a cell connection and/or Touch ID enabled?
A delayed rollout sounds like a good idea. Though I don't expect Apple will do that.
Thanks on the cat. That's not a photo of my Puma, but it looks just like him!
I used to be the Software Quality Assurance (QA) Manager for a multi-million dollar company out of the Seattle area a few years ago before I quit to start my own software company.
The fact that this got through from a company like Apple is unacceptable. The way I see it, NO testing was done with over-the-air updates on multiple carriers and Touch ID. NONE. Who ran the test cases here? And this is from a multi-BILLION dollar company.
Whoever let this through the QA process for iOS releases should be fired.
E
The fact that this got through from a company like Apple is unacceptable. The way I see it, NO testing was done with over-the-air updates on multiple carriers and Touch ID. NONE. Who ran the test cases here? And this is from a multi-BILLION dollar company.
Whoever let this through the QA process for iOS releases should be fired.
E
No thank you, whilst there's that that'd be "fixed" I'd also miss a bunch of things introduced with iOS8.
Kinda pick your poison.
I'm not really expecting Apple to revert this error by design. I'm well aware they will keep it that way and justify it with a product I'll steer clear from: Photos in the Cloud.
Glassed Silver:mac
This isn't an 'Ooops!', this is a 'WTF!!!'.
Ahh, this reminds me of the good old days...
Windows NT patches that mysteriously brought back fixed bugs, only to be patched again, and bring back the bug that the patch that brought back the bug was supposed to fix.
The good old days...
----------
Apple could have included small steel rods inside the sides of both devices, just to keep it nice and flex free. Or design it so that 'flexing' is part of it's functionality...
Ahh, this reminds me of the good old days...
Windows NT patches that mysteriously brought back fixed bugs, only to be patched again, and bring back the bug that the patch that brought back the bug was supposed to fix.
The good old days...
----------
Apple could have included small steel rods inside the sides of both devices, just to keep it nice and flex free. Or design it so that 'flexing' is part of it's functionality...
YES!! I got blasted yesterday in another thread regarding this same logic. I was called an Apple fanboy idiot because I said that it probably wasn't a good plan for a user who had an important business call in 30 minutes to decide to update iOS on his phone within minutes of it being released (yes 30 min prior to this "important call")...............And I am the idiot!
He did correct me that it was an hour before his call not 30 minutes like he posted.
Anyway good advice and standard practice for IT in a business.
How much of this can be attributed to them having teams that work on multiple projects? They need to hire more people it seems. They need dedicated teams for each area of responsibility. They are stretching these people thin.
I'd gather the number of people who would actually have updated and who don't have a computer is probably extremely low.
Think about the type of person who generally updates software within an hour of its release (I'm talking small point updates - release date is generally unknown until it pops up). We're talking those of us who sit on Macrumors or other tech sites all day.
Like the bending, the scope of this is blown out of proportion.
Again, Apple should do better - I was shocked they let it out the door. But ultimately, it's people like me who updated and we know how to restore.
And for the few who don't, it's nice Apple Stores exist....there are lots of guys and gals in blue shirts that can take care of them.
He probably uses a Note 3 so it won't bend in those tight jeans of his.
LOL! This made my day bro
YES!! I got blasted yesterday in another thread regarding this same logic. I was called an Apple fanboy idiot because I said that it probably wasn't a good plan for a user who had an important business call in 30 minutes to decide to update iOS on his phone within minutes of it being released (yes 30 min prior to this "important call")...............And I am the idiot!
He did correct me that it was an hour before his call not 30 minutes like he posted.
Anyway good advice and standard practice for IT in a business.
What IT department doesn't take at LEAST weeks to internally test new software before rolling it out to the company? I'm baffled that people don't understand this.....
----------
iCloud Photos is FAR better than the old way.....duplicates taking up extra space, not syncing/saving across all my devices....Photos was a mess before iOS 8.
This is why I always wait to update iOS. 8 Doesn't have one single feature that I have been waiting on so I don't see the point in rushing. I will keep iOS 7 until I am about to buy an iPhone 6 Plus, which will probably be around Christmas, then I'll upgrade. Hell, I may wait until the (s) comes out next year. My 5s is still running strong... well no I take that back. I need more gb space. Damn you apple.
Problem with iPhone 5, Too
Two days ago, my iPhone 5, with iOS 8 installed, shut itself off. It took a soft reset to turn it on. The phone worked, but 3G didn't. I was limited to LTE, which eats up my data plan. I had temporary success at a fix restoring my iPhone via iTunes but the problem has returned.
So it's not just this first update that has an issue, at least for me.
Two days ago, my iPhone 5, with iOS 8 installed, shut itself off. It took a soft reset to turn it on. The phone worked, but 3G didn't. I was limited to LTE, which eats up my data plan. I had temporary success at a fix restoring my iPhone via iTunes but the problem has returned.
So it's not just this first update that has an issue, at least for me.
iOS 7.0.1 was release on Sep 19th, 1 day after iOS 7.0.0. Overall I'm not sure this was "fast-track" per se (I suspect they had this in testing prior to even releasing 7.0.0), but I bet you're right that the process went off the rails in the last week or so when they found the HealthKit bug. I bet they added fixes for that, and did some new builds, screwed it up, and didn't catch it in QC.
For an update like this one they can easily release it at almost any time when they feel it's ready to go.
----------
And yet you insult them anyway even though you admit that it actually serves a beneficial purpose to most others. Nice work.
my visits to macrumors are becoming shorter lately. reading through the supposed bending issue comments and those about 8.0.1 makes me think that either the forums are infested with trolls or that the collective IQ of apple users is getting desperately lower. It used to be a place where you could get interesting and reliable information. It is not that place anymore. Macrumors should rename itself macchatter or something
YES!! I got blasted yesterday in another thread regarding this same logic. I was called an Apple fanboy idiot because I said that it probably wasn't a good plan for a user who had an important business call in 30 minutes to decide to update iOS on his phone within minutes of it being released (yes 30 min prior to this "important call")...............And I am the idiot!
He did correct me that it was an hour before his call not 30 minutes like he posted.
Anyway good advice and standard practice for IT in a business.
I had the same reaction as you. Man if I was "waiting on some important calls", or out in the middle of nowhere where I needed my phone, the LAST thing I'd do is launch a software update! To me that's just crazy.
However, I can also understand that people are put off by this line of reasoning because they would argue that Apple released a product, not beta and not "special test try at your own risk", but a real shipping product. They made it available for OTA and iTunes updates, and gave you a notification to update (if you checked). Why shouldn't a person trust Apple and update at that point - are we really supposed to presume everything is broken until proven otherwise?
Plenty of blame to go around. But man, seriously, I wouldn't update when I'm in desperate need of my phone. I didn't update this time for that very reason, so I didn't get bitten by this issue.