Not part of this, but I have experienced in the past sporadic download corruptions with users. I've never figured out the exact cause, but a reinstall has always solved it. It's been roughly 10-15 users out of 25000 or so purchases. My best guess is that some part of the distribution pipeline does not fully validate the app package and re-download it if it fails.
I noticed something even odder when I was updating Instapaper from 4.2.2 to 4.2.3 on my iPad 2, iOS 6 beta 2 yesterday: Instapaper is about 25 megabytes, and I'm on a desperately slow network. It should've ended in no less than 5 minutes, but it just took over 15 seconds.
I'm certain that I'm on iOS 6 ( :D ), and I'm certain that I updated Instapaper (4.2.2 crashed on lunch in iOS 6, that's why he sent out 4.2.3 and now I can open Instapaper), and that my network is slow and it shouldn't have taken less than 5 minutes. So, what's the story? To my knowledge, delta updates are still not available to iOS apps for some reason. And I couldn't find anything about them in devforums/iOS 6 docs/WWDC sessions.
So, could it be relevant? Maybe they were testing delta updates by mistake and some apps got burned?
I have two waiting-for-review updates that have been sitting in the queue for 9 days now. This seems much longer than my past experience of 2-4 days turn-around. I wonder if these delays are related to the corrupt updates issue.
We had a app finally get thought the review queue last week after a 12 day wait. Maybe there's a recent surge of apps hitting the store post-WWDC? No problems with corrupted binaries for us though.
One of my apps went into "In Review" status at midnight (19 hours ago) and still hasn't been rejected or approved. The rejection or approval has always happened in less than 12 hours for me, so it seems like Apple might be holding all approvals until they've resolved this issue. At least, I hope that's the case... I really feel for the developers who got a slew of one-star reviews because of this.
Not possible without rejecting the binary unfortunately. If you submitted it a day ago or so, just reject it. It'll get dropped down in the queue but if the situation calls for it, might be necessary.
In the same spot. We have multiple apps with updates, partly to get our keywords back together after the "Chomp" store search update. I had been hoping we'd get reviewed in the next day or two, but now I'm happy to wait a few more days so we don't hit this issue.
Ugh, the need to delete the corrupt version and then install the good version also gets rid of all user data. What a mess.
Of course, this could be fixed by slightly increasing the version number or some other way to let iOS know that the good version is to be installed as an update over the broken one.
I suspect the issue isn't with the store corrupting binaries but the application servers being under heavily load and dropping connections to the user. Begs the question why they aren't doing MD5 validation of the binaries before launching and notifying the user.
It is 4th July holiday after all. Lot more traffic.
They're distributed as .zip files (renamed .ipa), so a corrupted file or bad download wouldn't extract anyway. The real issue here is in their DRM: they have to re-encrypt the binary for each user, and the encryption seems to be incorrect in some cases. That's also consistent with the FairPlay log error in Marco's post.
[+] [-] smokey_the_bear|13 years ago|reply
It seemed to effect US users around noon PDT, and then a batch of international users around 5 pm PDT.
[+] [-] andrewljohnson|13 years ago|reply
I also sent the App Review team an email asking if they will expunge all the bad reviews once this is over, but I doubt that's going to happen.
[+] [-] rbritton|13 years ago|reply
[+] [-] pooriaazimi|13 years ago|reply
I'm certain that I'm on iOS 6 ( :D ), and I'm certain that I updated Instapaper (4.2.2 crashed on lunch in iOS 6, that's why he sent out 4.2.3 and now I can open Instapaper), and that my network is slow and it shouldn't have taken less than 5 minutes. So, what's the story? To my knowledge, delta updates are still not available to iOS apps for some reason. And I couldn't find anything about them in devforums/iOS 6 docs/WWDC sessions.
So, could it be relevant? Maybe they were testing delta updates by mistake and some apps got burned?
[+] [-] rkudeshi|13 years ago|reply
[+] [-] scottchin|13 years ago|reply
[+] [-] mmsear|13 years ago|reply
[+] [-] thetron|13 years ago|reply
[+] [-] terhechte|13 years ago|reply
[+] [-] deeje|13 years ago|reply
[+] [-] markerdmann|13 years ago|reply
[+] [-] dave1619|13 years ago|reply
[+] [-] scottchin|13 years ago|reply
[+] [-] gauravk92|13 years ago|reply
[+] [-] ja27|13 years ago|reply
[+] [-] bryanjclark|13 years ago|reply
[+] [-] leberwurstsaft|13 years ago|reply
Of course, this could be fixed by slightly increasing the version number or some other way to let iOS know that the good version is to be installed as an update over the broken one.
[+] [-] alttab|13 years ago|reply
[+] [-] unknown|13 years ago|reply
[deleted]
[+] [-] n9com|13 years ago|reply
[+] [-] samstave|13 years ago|reply
[+] [-] jordanclark|13 years ago|reply
[+] [-] taligent|13 years ago|reply
It is 4th July holiday after all. Lot more traffic.
[+] [-] Xuzz|13 years ago|reply
[+] [-] thought_alarm|13 years ago|reply
Christmas day is the big one for the App Store. I doubt July 4 comes very close to that.
[+] [-] bobbypage|13 years ago|reply