11–20 of 51 posts
It is 4th July holiday after all. Lot more traffic.
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.
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.
Christmas day is the big one for the App Store. I doubt July 4 comes very close to that.
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.
If that were the case then it would affect all apps rather than a small handful of apps that updated yesterday. Christmas day is the big one for the App Store. I doubt July 4 comes very close to that.
Earlier quoted context omitted.
Does someone at Apple manually check the whole app when you submit an update?
Yes, absolutely. In fact, based on the fact that my apps frequently sit in 'In Review' (versus 'Waiting for Review') for 12+ hours usually, it wouldn't shock me if they had multiple people review each submission. How much they play around with the app seems to vary - I've had odd, hard-to-trigger bugs get my app rejected, even though they existed for several prior versions. Each app submission/update costs Apple a fa…
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.
If that were the case then it would affect all apps rather than a small handful of apps that updated yesterday. Christmas day is the big one for the App Store. I doubt July 4 comes very close to that.
Also July 4 is a pretty big holiday as far as usage patterns go.
This is also happening to our app, Gaia GPS, and it's pretty much ruining my holiday. It seemed to effect US users around noon PDT, and then a batch of international users around 5 pm PDT.
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.
Earlier quoted context omitted.
Yes, absolutely. In fact, based on the fact that my apps frequently sit in 'In Review' (versus 'Waiting for Review') for 12+ hours usually, it wouldn't shock me if they had multiple people review each submission. How much they play around with the app seems to vary - I've had odd, hard-to-trigger bugs get my app rejected, even though they existed for several prior versions. Each app submission/update costs Apple a fa…
The only time Apple gave out hard numbers on their review setup, a couple of years ago, they had two reviewers check each submission, with an average of 6.5 minutes per reviewer per submission spent checking it. Obviously, that average contains quite a bit of variation.
Earlier quoted context omitted.
Yes, absolutely. In fact, based on the fact that my apps frequently sit in 'In Review' (versus 'Waiting for Review') for 12+ hours usually, it wouldn't shock me if they had multiple people review each submission. How much they play around with the app seems to vary - I've had odd, hard-to-trigger bugs get my app rejected, even though they existed for several prior versions. Each app submission/update costs Apple a fa…
The only time Apple gave out hard numbers on their review setup, a couple of years ago, they had two reviewers check each submission, with an average of 6.5 minutes per reviewer per submission spent checking it. Obviously, that average contains quite a bit of variation.