Alex Rivera | Logout

Invalid Binary Itunes Connect

Asked 2011-01-25T16:57:28.603
35

Possible Duplicate:
Invalid iPhone Application Binary

Im ripping my hair out over this!!!

I have tried like everything and evertime i submit my app to itunes connect it allways says:

Upload Received

(2 minutes Later)

Invalid Binary

Its Driving me mad and i have already:

  • Cleaned all builds

  • Made a new Entitlement.plist

  • Checked that it built with The Distribution Profile.

Edit
Report

3 Answers

3

I fixed this by adding two new keys to my entitlements plist - application-identifier and keychain-access-groups:

<plist version="1.0">
<dict>
    <key>application-identifier</key>
    <string>T9YRD11G97.com.duncancampbell.fontagious</string>
    <key>get-task-allow</key>
    <true/>
    <key>keychain-access-groups</key>
    <array>
        <string>T9YRD11G97.com.duncancampbell.fontagious</string>
    </array>
</dict>
</plist>

I got the "T9YRD11G97" from AppID in the provisioning profile, and the "com.duncancampbell.fontagious" from the BundleID in iTunesConnect.

Hope this helps.

answered 2011-06-29T08:19:32.047
1

When attempting to update my app, I experienced this problem as well. The only real change to my app since I last submitted it was the addition of iCloud support. I suspected something was wrong with my entitlements, and the error email I got from the itunesconnect@apple.com submit bot was very fishy. The relevant portion read:

Specifically, value "XXXXXXXXXXX.com.mydomain.myappmame" for key
"com.apple.developer.ubiquity-container-identifiers" in 
MyAppName is not supported.

I've anonymized the app/domain/team id here to MyAppName / mydomain.com / XXXXXXXXXX. Note that the complaint says "XXXXXXXXXXX.com.mydomain.myappmame" is incorrect. Indeed it is incorrect. It should be "myappname", not "myappmame" with an 'm' instead of 'n'. I looked in the entitlement file in my project, and it was correct. I looked at the entitlement file included in the app bundle I submitted to the store, and it was correct. I unzipped the zip file I submitted to the store, and the entitlements file was correct there as well. So clearly this character substitution was happening after the app submission was accepted by the App Store.

Surely this problem doesn't affect everyone, or there would be a mass outcry. So I figured it likely that there's something "special" about my app that invokes a bug in the automated App Store submit processing. To verify, I created a new empty app from scratch, enabled iCloud entitlements, and submitted it to the App Store with a new app identifier. It was accepted and status changed to "waiting for review". So it passed muster. (I rejected the binary immediately so it wouldn't be reviewed :)

I managed to work around the problem by changing my entitlements file:

<plist version="1.0">
<dict>
    <key>com.apple.developer.ubiquity-container-identifiers</key>
    <array>
        <string>$(TeamIdentifierPrefix)com.mydomain.myappname</
answered 2012-03-10T22:59:11.173
0

In my Case I expand the CFBundleIcons dictionary and then checked the icon name in CFBundleIconFiles. there was the old name of my icon so I updated it and it worked for me.

answered 2012-05-26T18:25:47.693

Your Answer