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 just got mail from apple

Missing 64-bit support - Beginning on February 1, 2015 new iOS apps submitted to the App Store must include 64-bit support and be built with the iOS 8 SDK. Beginning June 1, 2015 app updates will also need to follow the same requirements. To enable 64-bit in your project, we recommend using the default Xcode build setting of “Standard architectures” to build a single binary with both 32-bit and 64-bit code.

So please remember to add arm64 as valid architecture in project target settings as well as project settings

Now add arm64 by

And it will look like

Answer 2

The trick of the IPad icon do work.

Remove the CFBundledIconFiles~ipad and add a 72x72 icon to the Icon Files key

Beware with the screenshots, this method sometimes, creates the Missing Screenshots Error

Answer 3

Thanks to everyone who proposed solutions. As it turns out, none of your suggestions helped in my case, but I did solve the problem. Here's what worked for me:

Delete Entitlements.plist from your project. Then do Add -> New File and re-add Entitlements.plist.

The format of the Entitlements.plist changed between SDK 3.1.3 and 3.2. If your Entitlements.plist was created with an SDK earlier than 3.2, and you're now trying to update your app using SDK 3.2 or greater, it appears that you have to delete the Entitlements.plist and re-add it using the new format. Otherwise Apple will reject your upgrade as an "Invalid Binary".

Answer 4

I have same issue. Make sure you have choosen "App Store" as distribution method in distribution provisioning profile, not "Ad Hoc".

Answer 5

Another possible option, received this error message after resubmitting the binary a few times:

Your Info.plist contains the UINewsstandIcon sub-property under CFBundleIcons, which is intended for use with Newstand features. To include Newsstand features, the Info.plist must include the UINewsstandApp=true Info.plist key.

Check your info.plist — I didn't add that property myself, and didn't get any errors during local or Testflight testing.

Answer 6

Same problem, different solution: my archive scheme was using ad hoc build configuration, when it should have been release.

Checklist for my failed fix attempts at my blog Application Failed Codesign Verification.