What can cause “invalid binary” with no email followup from iTunes Connect?

Question

I\'m trying to submit an update of an existing application on behalf of one of my clients, and I\'m getting \"Invalid Binary\" failures from iTunes Connect with no explanati

Answer 1

I had the same problem and it was apparently tied to the size of the Default startupscreen image shipped with the app.

I was sending 1024x768 default image but I have find in this article :

http://weston-fl.com/blog/?p=840/

That it needs to be 1024x748 (for a landscape default) and I seems it worked : iTunesconnect took it after that.

Answer 2

i had this problem. my issue turned out to be setting the deployment target to something less than 3.2, but having the architecture still set to 'optimized for armv7.' this is using xcode 3.2.3. the latter setting should be changed to 'standard (armv6 and armv7).' when i'd built my development app, i had to change it, because xcode complained when i tried to run the app on an older itouch, but with a distribution build there's no device to run on (unless you test with an ad hoc first), so you don't notice the problem until itunes connect rejects the binary.

Answer 3

I faced the same problem, tried with most of the solutions and finally come to below solution.

Just Check following things..

1) add arm64 as valid architecture in project target settings as well as project settings

2) Modify info.plist file and add Icons files array with all required images with name.

3) Most important -- because of rejection you changed the version number of application in plist file but not on iTunes portal.
You need to set/manage same version number in app and on iTunes portal. Set this and try to upload binary again,this will resolve your problem.

Answer 4

2015

The Invalid Binary issue can now be caused if EMBEDDED_CONTENT_CONTAINS_SWIFT is true, but fail to actually include any Swift code in the binary.

Go ahead and falsify this value in the application build settings.

Xcode had also included User-Defined Settings that included the word Swift - I just went ahead and culled that too.

Answer 5

Currently (May 8 2013) this error is thrown if you access UDUD in your app. MKStoreKit (a popular open source library) does, and that was what was causing it for me. Search for the following method below in your files (assuming it's not in a precompiled binary, in which case, go google whatever you have and check their release notes)

[UIDevice currentDevice].uniqueIdentifier

Answer 6

I've been struggling with the same problem for quite a while now. I discovered this morning that the team agent had all the notifications turned off, so I turned them all on and finally started getting state change emails when the app changed to "Waiting For Upload", but still nothing when the state changed to "Binary Invalid". After a few more attempts, I finally got the app update into the "Waiting For Review" state. What solved it for me was changing the value of "iPhone OS Deployment Target" in the target's build settings from iPhone OS 2.2.1 (the setting for the original app) to iPhone OS 3.0.