And by "forever", I mean, it is going on two weeks now and several of the builds are still stuck in "Processing".
The only clue I have is that the builds that get stuck in this processing state are builds that include a specific third-party framework that is, unfortunately, required for the product.
When I upload a build without the framework, it goes through processing quickly and is ready for testing within minutes usually.
If I upload a build with this framework, it never gets past the "Processing" state.
I went through a week of speaking with Apple App Store developer support about this issue, and believe it or not, they had no answers and suggested I post on the forums. Like, for real, that is what they said.
So this is my shot in the dark, that somewhere, someone has had an issue with eternal "processing" situations and figured out how to resolve the issue.
Note: This is a tvOS app and not an iOS app.
The only clue I have is that the builds that get stuck in this processing state are builds that include a specific third-party framework that is, unfortunately, required for the product.
When I upload a build without the framework, it goes through processing quickly and is ready for testing within minutes usually.
If I upload a build with this framework, it never gets past the "Processing" state.
I went through a week of speaking with Apple App Store developer support about this issue, and believe it or not, they had no answers and suggested I post on the forums. Like, for real, that is what they said.
So this is my shot in the dark, that somewhere, someone has had an issue with eternal "processing" situations and figured out how to resolve the issue.
Note: This is a tvOS app and not an iOS app.
Update: Problem has been found. The 3rd party framework has an invalid UIDeviceFamily in their info.plist file. The framework has both "3" and "5" as properties, but the app and framework is only for tvOS (which is "3").
Interestingly, Apple developer support kept insisting that the app was getting stuck in "processing" because it was too large - which at a whopping 24 MB (compressed @ 12 MB compressed) seemed a little far fetched to me.
So as I was going through the steps of proving that the app was indeed only 12 MB, I decided to an AdHoc build locally and export it so I can send it to the Apple dev support engineer.
Well, that produced the first clue - as exporting that archive failed with the following error:
Apparently a UIDeviceFamily of "5" is the Apple HomePod. I have no idea why the info.plist for the 3rd party library includes this in their info.plist file for a framework that is tvOS only - but that was the problem. I was able to edit the .plist file and remove the "5" from the UIDeviceFamily list and it now processes immediately on the TestFlight app store.
The interesting thing in all of this is that I never saw a warning or error when archiving and uploading to the App Store. It was only when I tried to export an AdHoc build that the export process produced and error.
Interestingly, Apple developer support kept insisting that the app was getting stuck in "processing" because it was too large - which at a whopping 24 MB (compressed @ 12 MB compressed) seemed a little far fetched to me.
So as I was going through the steps of proving that the app was indeed only 12 MB, I decided to an AdHoc build locally and export it so I can send it to the Apple dev support engineer.
Well, that produced the first clue - as exporting that archive failed with the following error:
Code Block ipatool failed with an exception: #<RuntimeError: Unknown UIDeviceFamily: '5' from '[\"3\", \"5\"]'
Apparently a UIDeviceFamily of "5" is the Apple HomePod. I have no idea why the info.plist for the 3rd party library includes this in their info.plist file for a framework that is tvOS only - but that was the problem. I was able to edit the .plist file and remove the "5" from the UIDeviceFamily list and it now processes immediately on the TestFlight app store.
The interesting thing in all of this is that I never saw a warning or error when archiving and uploading to the App Store. It was only when I tried to export an AdHoc build that the export process produced and error.