originally posted by Jade on the invalid binary error after a several hour fight to determine what the issue was uploading a client’s app:
Invalid Binary.
Gee thanks Apple for that insightful, descriptive message. Surely with all your advanced binary scanning, static analysis, Application Uploader, etc. all you can give us is a most unhelpful “Invalid Binary”?
If you are suffering from “Invalid Binary” issues, and have done everything short of sacrificing small farm animals, try this trick.
If your Entitlements.plist file was generated with an version of Xcode prior Xcode 3.2.3, remove Entitlements.plist and regenerate it using Xcode 3.2.3. You don’t need to change any of the options generated on your new Entitlements.plist file, just recompile and submit again. Hopefully this helps someone.
This is a part of the cryptic “etc” Apple speaks of with the possible reasons for an “Invalid Binary” app rejection reason.
Hello there, your post was quite helpful. Searched itunes connect invalid binary on google, clicked here, saw that it was a simple Entitlements.plist error. Deleted and re-added mine, and I just submitted my app successfully withou the error that popped up before. Thanks a lot! 🙂
Great post. This is exactly what I needed to not rip any more hair out of my head when submitting. THANK YOU!