iOS 9.3.2 Bricking Some 9.7-inch iPad Pro Devices With 'Error 56' Message [Updated]

[ConnorMcJeebus]

This confirms his/her assumption for me.

When objects are promoted to QA the changes are tested against the requirements and regression tested. If a defected is found the object(s) are rolled back to development. After the bugs are corrected it's promoted back to QA for testing and regression testing again. So even though I'm not an Apple developer I can confidently answer your question: yes, the final build was tested. Christ.

And no, Apple doesn't get a pass when things don't go perfectly.

I think she/he meant "did nobody bother to test the final release build [for this specific bug that is affecting many users, because if they did, then it probably would have been identified and corrected before public release." That would make more sense to me, anyways.

 

[hpaulh]

You all need to slow down and stop commenting if you "don't" even own an iPad Pro. I do own an iPad Pro 9.7!!! My update installed flawlessly over Wi-Fi, and my iPad has been working without a hitch. There must be a bunch of you who just like to bash Apple. But if you don't own the hardware, stop handling the fruit!

 

[Steve J0bs]

You all need to slow down and stop commenting if you "don't" even own an iPad Pro. I do own an iPad Pro 9.7!!! My update installed flawlessly, and my iPad has been working without a hitch. There must be a bunch of you who just like to bash Apple. But if you don't own the hardware, stop handling the fruit!

My 9.7" Pro is bricked. So don't speak for everyone.

 

[dk001]

Well now there are more possible update scenarios to check. The number of devices supported has increased. Then the iPad can be Wi-Fi only or LTE and older devices have CDMA or GSM versions and then you have updates through itunes or over the air and finally there is the history of the device (was it registered to different itune accounts in the past).I don't want to do the math but there are a lot of scenarios. For example on a recent update there was a specific problem that only happened with iPad 2 GSM with an over the air update. They should check all of these of course but frankly I am not surprised some things are falling through the cracks.

True however it looks really really bad when it is your new just released top of the line Pro. That I would have thought would have been one of the items over-tested.

 

[AdeFowler]

Totally not risking it

Same here. I can't be without my iPad and I live miles away from an Apple Store.

 

[hpaulh]

My 9.7" Pro is bricked. So don't speak for everyone.

I'm not speaking for everyone. But maybe your problem isn't the update, maybe it's something on your iPad. We just don't know yet, do we?

 

[Alenore]

You all need to slow down and stop commenting if you "don't" even own an iPad Pro. I do own an iPad Pro 9.7!!! My update installed flawlessly over Wi-Fi, and my iPad has been working without a hitch. There must be a bunch of you who just like to bash Apple. But if you don't own the hardware, stop handling the fruit!

You should slow down and stop comenting if you're not experiencing the bug.
I do.

 

[bigpics]

It's at the point I would NEVER have updates set to auto, nor download one before at least until a week has passed....

....and just endemic with all the other small, but cumulative wheels that seem to be coming off the Apple cart....

 

[Alenore]

I'm not speaking for everyone. But maybe your problem isn't the update, maybe it's something on your iPad. We just don't know yet, do we?

So the problem is on our iPad but it only showed up when we updated it...
It doesn't make sense.

 

[hpaulh]

Every damn iOS update! Quality control has absolutely gone down the toilet over there! The part I don't get is how this managed to slip through 4 betas unnoticed.

Prove to me you even own an iPad Pro!!!!

I do own an iPad Pro 9.7!!! My update installed flawlessly over Wi-Fi, and my iPad has been working without a hitch.

 

[petsounds]

True however it looks really really bad when it is your new just released top of the line Pro. That I would have thought would have been one of the items over-tested.

This is I believe the second time the Pro mini has had a software issue specific to it. Makes me wonder if there's a hardware-specific feature, such as the TrueTone display, that has some lingering bugs.

 

[lakerchick4life]

The way I always update my iPads is that I connect it to my PC(Already downloaded the latest iTunes) then first download the update, DFU the iPad, then install the firmware..if doing this also causes the brick I wont touch this update til there is a fix

 

[hpaulh]

So the problem is on our iPad but it only showed up when we updated it...
It doesn't make sense.

Wait and see. Maybe you'll learn something.

 

[ConnorMcJeebus]

You all need to slow down and stop commenting if you "don't" even own an iPad Pro. I do own an iPad Pro 9.7!!! My update installed flawlessly over Wi-Fi, and my iPad has been working without a hitch. There must be a bunch of you who just like to bash Apple. But if you don't own the hardware, stop handling the fruit!

I'm not speaking for everyone. But maybe your problem isn't the update, maybe it's something on your iPad. We just don't know yet, do we?

Prove to me you even own an iPad Pro!!!!

I do own an iPad Pro 9.7!!! My update installed flawlessly over Wi-Fi, and my iPad has been working without a hitch.

Oh boy.

 

[Chupa Chupa]

I'm not speaking for everyone. But maybe your problem isn't the update, maybe it's something on your iPad. We just don't know yet, do we?

Then that would be the s/w. iOS and the App store are gated. Apps should not be able to be destructive, that is why Apple insists on the App store being "members only," so it can sift out the dangerous stuff.

Look it happened. Hopefully people backup their iPads regularly. PITA, but ultimately, everything will be brought back to normal, but no reason to get defensive or blame the victim. Apple goofed. No one said they were perfect. Hard to be with as many different devices that run iOS and OS X now. Things like this are bound to happen, just the nature of it when things have to move as fast as they must these days.

 

[speedlimiter]

I agree they should have spotted this but it's a bug in the latest firmware and wasn't present in the beta's.

It was in the last beta. I contacted Apple two weeks ago because of this.

 

[falainber]

So the problem is on our iPad but it only showed up when we updated it...
It doesn't make sense.

And considering the fact that all software installed on your iPad was certified by Apple...

 

[weup togo]

Sounds like brand new iPad Pro 9.7" 128GB and 256GB configs are affected. These are the units that will have the least internal exposure within the company, because a) they're new b) they're expensive and CTO, so they're going to purchase as few as possible.

People bitching about this thread should remember that warnings about things like this from MacRumors might actually help some folks avoid hitting the issue, if they would. And yes, millions of people see MacRumors headlines whenever they make it to the front page of news.google. It doesn't take much to get the word out and spread caution. New OS updates don't automatically show up on everyone's devices, until Apple flips a second switch. The only people who have installed so far deliberately went looking for an update. The more of those folks warned off, the better the world is, until Apple can get its act together.

 

[bernuli]

I wonder if Tesla has ever bricked a car after a software update.

 

[Deasnutz]

while Apple is quick to fix these issues, if ithas the potential for data loss I think they should pull it (for IPP at least).

 

[David_Howard]

This confirms his/her assumption for me.

When objects are promoted to QA the changes are tested against the requirements and regression tested. If a defected is found the object(s) are rolled back to development. After the bugs are corrected it's promoted back to QA for testing and regression testing again. So even though I'm not an Apple developer I can confidently answer your question: yes, the final build was tested. Christ.

And no, Apple doesn't get a pass when things don't go perfectly.

Regression and/or Unit testing is not the same as real world beta testing in the field. Clearly they changed something after beta 4 and it passed normal automated tests. Isn't the release when it counts?

 

[TheItalianDude]

Did Apple outsource their QA department or something? Everyone makes fun when Microsoft has a bug, and they test on hundreds of devices... how many variations of iOS devices are there? Like 3?

There's no excuse for this poor quality, I thought software and hardware working together as one, no?

They have :
IPod touch
Ipad
iPhone

But then
They have to make it stable for :
iPad 2 wifi only and 3G CDMA/GDM
IPAD 3 wifi only and 4G CDMA/GSM
iPad 4 wifi only and 4G CDMA/GSM
iPad Air wifi only and 4G CDMA/GSM
iPad Air 2 wifi only and 4G CDMA/GSM
iPad mini wifi only and 4G CDMA/GSM
iPad mini 2 wifi only and 4G CDMA/GSM
iPad mini 3 wifi only and 4G CDMA/GSM
iPad mini 4 wifi only and 4G CDMA/GSM
iPad Pro 12.9" wifi only and 4G CDMA/GSM
iPad Pro 9.7" wifi only and 4G CDMA/GSM

iPhone SE
iPhone 6s
iPhone 6s Plus
iPhone 6
iPhone 6 Plus
iPhone 5s
iPhone 5c
iPhone 5
iPhone 4s

iPod touch 5
iPod touch 6

So as you can see realistically they have to do testing for much more than 3 iOS devices looking at that list a bug is going to slip in somewhere no matter if the hardware is new or old

 

[Lobwedgephil]

Sounds like brand new iPad Pro 9.7" 128GB and 256GB configs are affected. These are the units that will have the least internal exposure within the company, because a) they're new b) they're expensive and CTO, so they're going to purchase as few as possible.

People bitching about this thread should remember that warnings about things like this from MacRumors might actually help some folks avoid hitting the issue, if they would. And yes, millions of people see MacRumors headlines whenever they make it to the front page of news.google. It doesn't take much to get the word out and spread caution. New OS updates don't automatically show up on everyone's devices, until Apple flips a second switch. The only people who have installed so far deliberately went looking for an update. The more of those folks warned off, the better the world is, until Apple can get its act together.

I have seen a couple of 32 also. No issues on my 256 luckily.

 

[sbailey4]

Every damn iOS update! Quality control has absolutely gone down the toilet over there! The part I don't get is how this managed to slip through 4 betas unnoticed.

Thats what I dont understand. Unless not enough users with the pro tests the beta software. I tested all the way from B1 on iPhone 6s and no real issues to speak of. Very solid version all the way through. However the release is 1 rev newer so maybe thats what broke things ( beta 4 was 13F68 and release is 13F69)

 

[ylim048]

Mine is bricked. Too bad...