Filed as a bug: 22658008
It's unacceptable that suddenly all builds uploaded (above 30mb or so, but these turn into 150mb or more when bitcode is included) take several hours or days even in Processing time. They don't come out of this state and it's impossible to test apps using TestFlight anymore. We sit and wait but testers run out of patience and bugs need to be identified and squashed in a timely fashion.
I talked to one of the supervisors, she will look into the issue with her engineering team. You could try to contact them by phone too, don't let them get away easy with this Beta stuff. The GM release is intended for submitting apps, this has to work. You could also file a bug report, the more they get the better. This is actually a very serious issue and ODR is clearly the culprit in my opinion.
Builds submitted using Xcode6 and Xcode7 since Sept 11 has been in "Processing" mode. No signs of progress, bitcode off, no ODR, no iOS9 specific code.
Can someone from Apple comment here? I understand that problems do occur (we are developers after all). But keeping developers in the dark is not a great experience.
Billy.
Same here. Stuck in "Processing". I have bitcode and iOS9/watchOS2 stuff enabled though. Tried to contact Apple, but no reply yet. At least I can stop trying stuff now because I'm convinced it's an Apple problem by now.
I haven't heard anything new from Apple yet, but my some of my builds finally finished processing (after 80+ hours).
However I found a workaround for those who have problems with ODR: I started with a binary with 27 ODR tags and 7000 image files in total (1.1GB). Processing took forever. I then zipped the images for every tag, ending up with 1 file per tag and a total of 900MB. Unzipping is done at runtime. I submitted this build and it finished ITC processing in 2 hours! So it seems the problem with processing is related to the number of files in the ODR tags.
Hope this helps
I got one which is stuck for a day... then it go through.
I got another one which is stuck for a day, then I resubmit a new one, then the new one go through (the first one remains in process).
Unchecking "Include bitcode for iOS targets" helped in my case.
Where I can find?
This is when you klick on "Upload to App Store" after archiving, before klicking on "Submit".
I can't find that option, I have bitcode turn off in the setting.
Tried this as well but didn't help.
Really a big mess from Apple side. This is a disaster. I am waiting since a week an answer by Apple, but my App is still "processing".
Thanks, I did the same. My ticket has been open with ITC since mid-week, but they have yet to give me any update on status.
My radar on this issue is 22544199, filed September 2.
Unfortunately, like others here my iOS 9 release is completely held up pending the resolution of this.
Interesting data point, thanks tober79.
Our app (also in eternal Processing) has about 30 Resource tags and only about 150 actual files scattered across those tags. But these files are around 64 MB each. However, our files are separated segments of a few very large files. For example, we have binary catalog files which are over a gigabyte in size, but broken into 64MB chunks.
Sounds like Apple may have different scanning processes based on file type, and zipped may be a faster path.
After waiting a whole week in which my app stucks in status "processing" and after several retries with incremented build numbers – all versions stalled "processing" – I tried today the upload of the .ipa file with the Application Loader. Additional, I had to switch off bitcode and symbol transfer for success. Now, the app prerelease was available after a couple of minutes. Maybe this result is by random or by luck …
I filed a bug and wrote two times to apple support with no response. This is really poor and – yes– a disaster.
Jochen
Today even my beta-builds from a month ago finished processing. So I assume they fixed something on the backend. Anyway, I am sticking with the zip workaround for ODR which gives me fast processing every time. Good luck everyone, I hope we can at least make it for the release of the iPhone 6S.