I spent the past week pulling out my hair trying to submit an update for Centare’s EyeOnWeather application to iTunes Connect. I kept getting a reject from the system and all I got for an error message was “Invalid Binary.” THANKS, THAT’S SOOPER.
Eventually I ended up attempting to contact iTunes Connect Support for further details. I thought it might have been missing icons, malformed Info.plist, something. I haven’t changed anything in the project drastically with how it builds, so I was at a loss. Turns out, I was picking the wrong provisioning profile in my setup. Man I felt stupid. Ends up that I’m not crazy – Apple’s documentation on how to set up your project for building still only references Xcode 3. Awesome for the rest of the world using Xcode 4. Here are some tips I got from Apple iTunes Connect support for pulling in information to submit to their developer team:
(replace 'path/to/myapp.app" with the actual path to your application): codesign --verify -vvvv -R='anchor apple generic and certificate 1[field.1.2.840.1136188.8.131.52.1] exists and certificate leaf[field.1.2.840.1136184.108.40.206.4] exists' /path/to/myapp.app codesign -dvv /path/to/myapp.app - This command is useful to see what certificate was used to sign your app. If under the section labeled "Authority" it says iPhone Developer, this means that your app was signed with your Developer Certificate. If it says iPhone Distribution, this means that it was signed with your Distribution Certificate. codesign -d --entitlements - /path/to/myapp.app
I ended up pulling the EyeOnWeather.app file out of my archive bundle to be sure I was testing what I sent up to iTunes Connect. You can also just do a “Build for Archive” and then right click your .app in Xcode under Product and “Show In Finder”. Drag that file into Terminal and it’ll paste the full path & filename.
Running those commands gave me confirmation of this – I was code signing with my developer profile. Even though you pick the Distribution certificate in the submission window for uploading, it doesn’t change the signature of the app. The solution was to go into my setup for the build and change the Code Signing Identity for the “Release” configuration to the Distribution profile. I deleted the old “Distribution” build configuration that I had created back in the Xcode 3 days as it’s no longer appropriate.
This link is the defacto WTF help me document for code signing in Xcode 4:
Technical Note TN2250 – Understanding and Resolving Code Signing Issues