Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I don't think pulling an update and working on a fix within a matter of days is slow to react. In such an industry where such updates aren't even pulled or such issues can be left out there for a long time until another update, this doesn't really seem slow. Sure, there's something to be said about hopefully not even having some of these issues to begin with, but that's a slightly different aspect of it all.

Let's be honest, they should have pulled it day 1.
 
Their quality control needs a lot of work. Next thing you know they'll start recalling hardware.

All this negative press will get to the average customer eventually, and that's when Apple will start feeling the pressure.
 
I have updated my iPad Pro 9.7 to iOS 9.3.2 and it is running smoothly and no error 56 message came up. The bricking is unfortunate that people experience but really I won't be afraid to update the phone when it comes out.
 
I swear things are different.
Looking at my phone when I go to Settings I see downloaded, not download or downloading. It then gives me the option to install.
It won't download automatically unless the device is plugged in and connected to WiFi. And even then it doesn't start right away the moment you plug it in. For me, it takes several days from the release date before such an automatic download happens (maybe I don't leave it long enough plugged in while connected to WiFi). Before that, you might even first have to tap on 'Check for updates'. Eventually it will download automatically but if you want it before that, you have to manually tap 'Download'.

Here are my update settings, always have been like this;
View attachment 632172
Something really strange. That is a quicktime recording of my screen. The time on my phone and Mac was identical at 18:36.
Those update settings only apply to app updates (and app, music or book purchases, note the 'new purchases' in the description below the setting switches).
 
Usually a matter of a day or two (if not just some hours) will do the trick. That said, with perhaps one or two exceptions, many of the update issues often didn't affect many people, so even when there are reports of people running into this or that it doesn't necessarily mean that you will or that even many do.

My 6 Plus was turned into one of the laggy, slow iPhones after the first IOS update was out and it took multiple versions before it was back to being snappy and quick again. If I had waited and seen what people were saying about it before updating I wouldn't have experienced it and wouldn't have updated for several versions. I learned my lesson.
 
Microsoft has pulled updates within 24 hours of issues being reported. Being slower to react than Microsoft is bad.
And they haven't in many other cases. Quite a lot of factors are involved in all of that, like what the impact is, what section of population is affected, what conditions apply, etc., etc., etc. It's not always or even mostly an on/off approach, short of basically fairly clear-cut cases where a huge section of the consumer base is quickly and obviously affected in a very similar manner.
 
I updated my pro the day the update came out and I couldn't get an appointment until Saturday to replace it. I hope they have replacement units in stock.
 
Yes, you must explicitly tap Install and enter your passcode in order for the correct tokens that gives iOS privileges to write software and firmware to be created. Those tokens expire after 12 hours (iirc). There is no way around this so it is impossible that a system with a passcode could be updated without the explicit approval of the person who has the piece to build that token.
I guarantee you I did not enter my passcode. I am explicitly against updating early on my phone. On my Mac not so much as I clone first and have a working system, (well two clones in fact), to revert to.
To say it is impossible is ridiculous. There are lots of things that don’t/won’t happen until Apple release the next software update to fix it. Remember that.
 
And they haven't in many other cases. Quite a lot of factors are involved in all of that, like what the impact is, what section of population is affected, what conditions apply, etc., etc., etc. It's not always or even mostly an on/off approach, short of basically fairly clear-cut cases where a huge section of the consumer base is quickly and obviously affected in a very similar manner.

It would have still been, and always is, a better idea to play it safe. If they had pulled it and it turned out to be false ... They lost nothing. In fact, pulling and investigating early makes them look better in the long run because it shows they care. They should not have left it out there while they investigated if the reports were right.
 
The only hint it gives me it that it's for setting for iTunes and Apps, not that it's for iTunes and Apps purchases made from other devices.
Maybe a pop-up explains it before the user commits but Apple could do a better job educating the user before they toggle. Even putting the use explaination on top of the toggles, next to "automatic downloads" rather than below it would be a human factors improvement.
Well, there is no harm done. Just because you are not aware that OS updates are not automatic, does not make them automatic. The only harm it does is that it might cause you to complain publicly (and thus harm Apple's reputation) that OS updates are/can be automatic.
 
It would have still been, and always is, a better idea to play it safe. If they had pulled it and it turned out to be false ... They lost nothing. In fact, pulling and investigating early makes them look better in the long run because it shows they care. They should not have left it out there while they investigated if the reports were right.
While I agree with the concept of what you are saying, that hasn't really been the practice in the industry (and even beyond the industry). It would be nice, just as many things would be nice, but reality doesn't seem to pan out like that for whatever reason. (Kind of similar--although certainly with enough differences--to when places prepare for some big storm that ends up being much smaller and then some people get upset that they "wasted" their efforts on preparations that weren't needed.)
 
  • Like
Reactions: American Hero
I don't understand the hate. This didn't happened to 100% of the devices. This is why I have Apple products. Software and hardware will always fail, and all we need is that the company take actions on these problems. I prefer that than waiting for the perfect product.
Perhaps, but we pay a premium for such products and there's an expectation that a software update will not render someone's tablet useless.

Imagine how people would slam Microsoft if it was reported here that the latest update bricked their Surface Pros - people would come out of the wood work saying how poor MS is, yet we have so many people here defending apple saying its no big deal. I'm not saying it a big or small deal, but I am saying that its an embarrassment for a company that chides itself on high quality.
 
What worries me is that iOS is the simpler software on lesser devices, what will happen to OS X that is a lot more complex and support a much larger product range?
 
While I agree with the concept of what you are saying, that hasn't really been the practice in the industry (and even beyond the industry). It would be nice, just as many things would be nice, but reality doesn't seem to pan out like that for whatever reason. (Kind of similar--although certainly with enough differences--to when places prepare for some big storm that ends up being much smaller and then some people get upset that they "wasted" their efforts on preparations that weren't needed.)

It might need to become the practice of the industry. For the culture of the industry to change, somebody has to be the first to do it. Apple should be that first.
 
  • Like
Reactions: SusanK
Apple made a big deal out of antennae-gate as well, giving out free bumpers and apologizing. Turns out it affected somewhere in the neighborhood of .01% of users. Maybe this is the same. Maybe it's .001% of users. Also, pulling the update is easy. I doubt they even had to move people from other projects. There are people bug testing software. The people working on this were never working on Maps (which is a data issue). They were never working on iTunes. They were never working on iCloud. I doubt the people working on iOS 9.3.2 (who are now working to fix it) were even working on iOS 10. Apple is a big company.
[doublepost=1463765929][/doublepost]

From what I can gather, it's something going wrong with a check when the update is validated. I'm guessing this is like the error 53, something we're not supposed to see but is a factory thing. You won the lottery, so to speak.
Antenna gate affected every iPhone 4....
 
  • Like
Reactions: weup togo
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.