iTunes Connect: Invalid Binary on submission

I'm trying to upload a new version of an app to iTunes Connect but everything I've tried so far has resulted in a Invalid Binary report by iTunes Connect. I have the Archive action set to Release and all schemes set to use the distribution certification and profile. Everything archives fine and the binary validates, but after uploading to iTunes Connect the binary moves into the Invalid Binary state and I get the following email:


Invalid Signature - Code object is not signed at all. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consulthttps://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html

Once these issues have been corrected, you can then redeliver the corrected binary.

Regards,

The App Store team

We are experiencing the same issue here. How Frustrating!

We've been using TestFlight for years now to feed our global sales team with our latest demos. Now do we not only have to re-upload the same code every 30 days, but now even uploading the same version that worked last week fails.


yikes.

Resolved.


Turns out this was due to a 3rd party framework. I removed the framework from the project and the binary submitted successfully after that. I'm not sure what Apple changed, but this was a huge headache to debug with absolutely no useful information regarding the actual issue.

iTunes Connect: Invalid Binary on submission
 
 
Q