ITMS 9000: The binary you upload was invalid

Question

When I ran into this issue, my first thought was to search Stack Overflow for solution. I did the search, found several topics. But, unlike my issue, those posters got

Answer 1

I ran into the same error when I tried validating my app. I got a message saying,

Unable to process app at this time due to general error

I searched on SO for this and only found a suggestion to wait for some time, as this is an error from Apple's servers. I tried all sorts of things, from playing with provisioning profiles to improving app performance and linking libraries, none of which resolved the issue. Unfortunately, I guess we don't have any other options than to wait and let Apple do its work.

Answer 2

Just spent a while on this also, my upload previously worked and managed to get through validation.

However, once up Apple would fail/reject the uploaded binary due to something similar to the below https://stackoverflow.com/questions/18952213/invalid-directory-name-your-app-contains-a-directory-name-that-is-already-rese#=

Upon retrying, later without making any modifications, rather then sucedding then failing after validation I started receiving an error exactly the same as the OP.

Fixing the framework reference issue, enabled me to succesfully upload.

So rather then uploading passing validation and then being rejected, it would not pass validation, and I give the same error, without any hints.

Hopefully this helps someone else.

Answer 3

iTunes connect (or at least some services that iTunes Connect uses) are down for the moment, so "Take a break for an hour, try again ..." is your best shot. Apple of course doesn't update their status page until tomorrow or so. https://developer.apple.com/system-status/

Answer 4

We found it wasn't necessary to revoke anything- when I went to Provisioning Profiles->Distribution, the two profiles for our two apps we were trying to release had been removed. I recreated those profiles (but I had to assign new names, using the old name led to a "profile already exists" message- so those identifiers are still out there- somewhere). Downloaded and installed the new profiles, resubmitted the archives we made on 7/18/14, and everything sailed right through.