Apple Pulls iOS 9.3.2 Update for 9.7-Inch iPad Pro After Bricking Complaints

This is Pro device for God's sake. Sold as a pro device that could replace a laptop. It is sold as a device that can change a professional's workflow. If I were a professional who's adapting to the new workflow and suddenly everything is gone because I am doing exactly what apple suggests (update your device), I would be so furious that you have no idea.
If you release a Pro device it has to be perfect. Always.
That is a completely different argument than saying they shouldn't have released 'too many' different products.
 
I swore you can block automatic updates..
There's no automatic updates really, but there are automatic downloads of iOS updates, which could be avoided if various steps are always taken or could be deleted after the fact, but no way to simply disable them.
 
My girlfriends iPhone 5 was "bricked" by he 9.3.2 OTA update as well. I put it in quote as it wasn't really COMPLETELY bricked, but she needed my help and Mac to restore 9.3.2 onto it and she lost photos she took since the last backup.

So it's not just iPad pros. Has anyone else had a device wedged by this update?

The bug doesn't allow you to restore the device. At least on iPad 9.7s.

I'm waiting for my replacement. They didn't have my configuration in stock so I'm without my iPad, probably until at least Monday.
 
My iPad Pro has twice needed restoring, the first thirty minutes out of the box after an upgrade to 9.3.1 bricked the device. The iPad crashes multiple times a day and the OS is wholly unstable (anyone who says "it's because there are more users" is clearly a moron).

I'd have returned it if the hardware wasn't as amazing.
 
Eh. Confused. Pls explain.
When an iOS updates is released, the Settings app will get a red badge and you might get a notification that a new OS update is available. To install it, you still have to tap 'yes' in the notification or manually go to Settings app and tap on download, agree, agree, install. Something requiring user interaction is not 'automatic'.
 
The specific set of circumstances that trigger this not being represented in their testing pool, including their public beta testing pool? I would expect that their public beta pool is pretty large, something hard to top with internal testing.

Maybe their testing procedures overlooked something that could have been included without increasing the testing pool significantly. But I rather think that fighting the underlying reason is an approach that is more likely to reduce such instances. That could start with having better programmers and better programming 'methods' that are able to predict and thus prevent circumstance that could result in such a failure. Maybe even the staggered release should be reconsidered, ie, if the 9.7" and 12.9" iPad Pro had been completely co-developed (and thus be as identical as possible internally) then it would be less likely that a bug affects only one of them (and if it affects both models, preventing and detecting it is easier).

I don't understand why they don't have 50 of every IOS device they sell and just have interns run updates on them than test functionality.

It may sound silly, but this bug probably wouldn't have gotten out..
 
You can. You can even block by category: apps or updates or everything.
There's no setting to block iOS updates (basically the automatic downloading of those updates when the device is plugged in and connected to a Wi-Fi network).
[doublepost=1463765051][/doublepost]
I don't understand why they don't have 50 of every IOS device they sell and just have interns run updates on them than test functionality.

It may sound silly, but this bug probably wouldn't have gotten out..
It still likely won't represent various configurations that might be out there in the wild as far as what's installed and how things are configured and how it's all used. That said, it does seem like either their pool of devices/testing needs to be expanded, or more attention needs to be paid to various tests that might perhaps be getting overlooked in one way or another.
[doublepost=1463765082][/doublepost]
Perhaps is a particular component that is causing the problem. Apple sometimes sources the same component from different vendors, thus explaining why some IPP 9.7s are bricking, and others are not.
There's something like that as well as far as different possibilities go.
 
You can. You can even block by category: apps or updates or everything.
App updates can be automatic, OS updates never are automatic. The setting in 'iTunes & App Stores' under 'Automatic Downloads' refer to (a) the automatic download of music, apps and books purchased on other devices and (b) the automatic download and install of app updates. They don't control OS updates.
 
How though? I’m talking blocking the download altogether.

Right. In iTunes and App Stores control panel there is a toggle for "automatic downloads" for Music, Apps, Books, and Updates. If you toggle any of those on iTunes will push the download to your device and install at night if your device is plugged in an on WiFi (cellular too if you allow that and its not a big app).

If you have that turned off the App Store app will still display apps that have updates but those have not yet been downloaded to your device. Maybe you are talking about not even allow the App Store app to show you what updates are available? But nothing is downloaded without your permission.
 
This is even more embarrassing considering there were 4 FREAKING BETAS......for an x.x.2 update.

Seriously what the hell is going on.....I think if Craig Federighi were held to the same fire Forstall was he would have been out a long time ago. Forstall was a jerk but at least this kind of crap wasn't going on with software on his watch.
 
Yes, you mean that you have unreasonable expectations for any company. Just because it's Apple doesn't mean there won't be problems. The sooner you get used to the idea the better. This isn't something new, either. Apple has never been a perfect company, and they never will be.

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.

That is a completely different argument than saying they shouldn't have released 'too many' different products.

see above. I think that by spreading too thin they might be unable to pay attention to details.
 
"This issue affects a small number of users" :rolleyes:

I think it's pretty clear that the reputation that Apple once had for stable software releases is sinking.


Oooh I personally think its sank to the deepest darkest depths of the ocean's already. From way back when the iPhone alarm stopped working because of the new year and Apple's advice was to 'wait 3 day's and then it would work again... They couldn't programme an alarm and calendar system to handle a new year.
 
I don't understand why they don't have 50 of every IOS device they sell and just have interns run updates on them than test functionality.
And what makes you think they don't do this already? There are millions of copies for most iOS devices out there, something that affects only 1% is unlikely to be caught by testing 0.005% of them. And that even assumes that the diversity Apple has in its 50 test devices is representative of the diversity of the actual devices in customers hands.

And note that they have a public beta program (I am on it). That covers probably more than 50 devices per specific device model. And this has not caught this bug either.
 
When an iOS updates is released, the Settings app will get a red badge and you might get a notification that a new OS update is available. To install it, you still have to tap 'yes' in the notification or manually go to Settings app and tap on download, agree, agree, install. Something requiring user interaction is not 'automatic'.
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. With 9.3.1 it started to prompt me that it would install automatically at 03:00 to which I chose, ‘Get lost’ and a few days later I noted that the update had been applied.
Here are my update settings, always have been like this;
Updates.jpg

Something really strange. That is a quicktime recording of my screen. The time on my phone and Mac was identical at 18:36.
 
Last edited:
App updates can be automatic, OS updates never are automatic. The setting in 'iTunes & App Stores' under 'Automatic Downloads' refer to (a) the automatic download of music, apps and books purchased on other devices and (b) the automatic download and install of app updates. They don't control OS updates.

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.
 
Apple pulls the update? This should have never happened in the first place and further complicate things for the iPad Pro users. So who gets the reprimand on this success of an update?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Back
Top