Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Meaning that that statement isn't true somehow?

Who knows how many users it's affecting but this is Apple's standard repsonse regardless of how widespread the issue is (at least most of the time) and it just shows the spin they put on everything. Reality distortion field at it's finest.
 
am so happy that this update was pulled now i can buy my LTE verizon ipad with out haveing too worry about it being brick after getting it i was holding off thanks too now i dont have too good job apple made me happy
 
Ah. Thanks for the clarification. I thought Apps were all apps and updates were all updates, but I didn't read the fine print in the app. So much for ease of use.
That the header for this whole section is 'iTunes & App Stores' should be a hint. And if you ever turned on the automatic downloads for apps, music or books, you would have gotten a popup explaining what turning it on meant (ie, automatic download of items purchased on other devices).
 
No, it's not unreasonable. I am asking that a brand new pro device, that is supposed to break a segment, has the deserved attention. We're not talking about a few devices here. We're talking about something of the magnitude that forced Apple to pull an update. In other words, it's much cheaper to pull the update and put engineers back to the drawing board (removing them from other projects maybe?) than exchange a few bricked devices. Why? Because it's more than a few bricked devices.
If you develop a new product, aimed at attacking a standard (the PC industry) you better not have this kind of issue.
On top of horrible Maps.
on top of the other iOS update issues.
On top of ugly iTunes.
on top of inefficient iCloud.
And so on.



see above. I think that by spreading too thin they might be unable to pay attention to details.

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]
I see. Thanks!

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.
 
This is EXACTLY why we should be able to block automatic updates.
My phone downloaded an update and it annoyed me as I have every setting I can think of set to NOT do that. Deleted it a couple of times and it happened again. So I left it this time.
Then it told me it would install in the middle of the night and I’m pretty sure I declined that too. Now guess what the update has taken effect - don’t know exactly when.
You must have relented at some point and tapped on 'Install' at some point (eg, on 'Install tonight').
 
  • Like
Reactions: HVDynamo
Ah. Thanks for the clarification. I thought Apps were all apps and updates were all updates, but I didn't read the fine print in the app. So much for ease of use.
Ok, so this clears it up for me. Thx.
[doublepost=1463766042][/doublepost]
You must have relented at some point and tapped on 'Install' at some point (eg, on 'Install tonight').
Maybe. Certainly wouldn’t use the term relented though. Would have been a mistake.
 
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.
I see. Some luck at last! Thank you for pointing this out for me.
 
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.
 
  • Like
Reactions: 997941
Having had one of the bricked devices, I am wondering if there is something hardware-related to it. Not all iPad Pro 9.7" models are affected, and there doesn't seem to be a rhyme or reason to it (e.g. it isn't as if it is just LTE or Wi-Fi models).
With no pattern emerging from the reports, I tend to agree. It also makes testing on Apple's side harder.
[doublepost=1463766348][/doublepost]
How about too many different devices now to test everything on all of them. There's are reasons Jobs simplified the lineup. Spreading a little too thin lately.
So what product would you kill (apart from the watch)? What older products should be cut from list still receiving updates?
 
That the header for this whole section is 'iTunes & App Stores' should be a hint. And if you ever turned on the automatic downloads for apps, music or books, you would have gotten a popup explaining what turning it on meant (ie, automatic download of items purchased on other devices).

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.
 
Who knows how many users it's affecting but this is Apple's standard repsonse regardless of how widespread the issue is (at least most of the time) and it just shows the spin they put on everything. Reality distortion field at it's finest.
Except that in many cases that is basically the reality.
 
I am still an Apple fanboy but I learned sometime ago to stop updating my gadgets immediately. I now always wait several weeks before doing so and this is another prime example of why.
 
Apple made a big deal out of antennae-gate as well, giving out free bumpers and apologizing.

I think you mean the press made a big deal out of it. Apple (SJ) initially blew it off. Apple only reacted when it was clear the reports were hurting the Apple brand. SJ fell on his sword and also gave out free swag and magically everyone was happy again.

I don't think this episode is a huge deal, but, again Apple is slow to react. That's what hurts them, that air of arrogance that it's always the user's fault.
 
I am still an Apple fanboy but I learned sometime ago to stop updating my gadgets immediately. I now always wait several weeks before doing so and this is another prime example of why.
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.
 
You must have relented at some point and tapped on 'Install' at some point (eg, on 'Install tonight').

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.
 
This is what happens when you play patty-cake with social issues and the 'green' ********. Knock it the hell off and get back to work! I can't pretend to have really known Steve, but I observed his track record, and he would have fired someone's ass by now.
 
  • Like
Reactions: Demo Kit and SusanK
I think you mean the press made a big deal out of it. Apple (SJ) initially blew it off. Apple only reacted when it was clear the reports were hurting the Apple brand. SJ fell on his sword and also gave out free swag and magically everyone was happy again.

I don't think this episode is a huge deal, but, again Apple is slow to react. That's what hurts them, that air of arrogance that it's always the user's fault.
That is my only concern, and the only thing I hope they change. Apple needs to react faster.
I don't think spending some time investigating something and 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.
 
I think you mean the press made a big deal out of it. Apple (SJ) initially blew it off. Apple only reacted when it was clear the reports were hurting the Apple brand. SJ fell on his sword and also gave out free swag and magically everyone was happy again.

I don't think this episode is a huge deal, but, again Apple is slow to react. That's what hurts them, that air of arrogance that it's always the user's fault.

That is my only concern, and the only thing I hope they change. Apple needs to react faster.
 
  • Like
Reactions: vlad_djkax
This is what happens when you play patty-cake with social issues and the 'green' ********. Knock it the hell off and get back to work! I can't pretend to have really known Steve, but I observed his track record, and he would have fired someone's ass by now.
Because there weren't all kinds of iOS or OS X issues with Steve around? (Rhetorical question, BTW.)
 
  • Like
Reactions: TMRJIJ
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.