The application-identifier entitlement is not formatted correctly

You must Login before you can answer or comment on any questions.

Titanium SDK: 2.1.3 Platform & version: iOS 6.0

When I distribute the apps in the step to valide the application in xcode. I get this errors:

This bundle is invalid. The application-identifier entitlement is not formatted correctly; it should contain your 10-character App ID Seed, followed by a dot, followed by your bundle identifier: com.companyname.appname (-19053)

And I google it. I found that I have to make sure the entitlement plist with the xxxxx.com.xxxx.appname. and yes all is there. but just cant passe the validation.

any one can help me? thank you so much

— asked 7 months ago by wei huang
5 Comments
  • Missing from your question are a number of important pieces of information. I suggest you take a look at the Using Questions and Answers article, specifically the Q&A Question Checklist. The missing information is critical to reproducing problems in a test environment and often indicates other factors that cause the undesirable outcome you are experiencing.

    — commented 7 months ago by Stephen Feather

  • Sorry is my mistake, so here is more details about the situation:

    I was trying to submit my app to the App store when the Xcode validation suddenly returned this error:

    This bundle is invalid. the application-identifier entitlement is not formatted correctly; it should contain your 10 character App ID seed, followed by a dot, followed by your bundle identifier: XXXXXXXXXX.com.mycompany.*
    My App ID in tiap.xml is 'com.mycompany.myappname' The generated Entitlements.plist file in the build contains:
    <?xml version="1.0" encoding="UTF-8"?>  
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
        <dict>
     
            <key>application-identifier</key>
            <string>XXXXXXXXXX.com.mycompany.myappname</string>
            <key>get-task-allow</key>
            <false/>
            <key>keychain-access-groups</key>
            <array>
                <string>XXXXXXXXXX.com.mycompany.myappname</string>
            </array>
     
        </dict>
    </plist>
    So everything seems fine. I have no custom Entitlements.plist file.

    My provisioning distribution profile also contains the right App ID string (XXXXXXXXXX.com.mycompany.*) and never gave problems in the past.

    I'm using: Titanium SDK 2.1.3 Xcode 4.5, IOS6, build for iPhone

    — commented 7 months ago by wei huang

  • ok something to try:

    In xCode organizer, remove the profile in question, agree to remove from drive (export your dev prof if worried first)

    Use the refresh icon lower right to pull down your certs and profiles (should be prompted to login to apple dev)

    Then in Tistudio, clean the project, then try to push to iTunes again (will have to locate the profile again from the drop down most likely)

    As an side, when was the last time you successfully pushed a build to apple?

    — commented 7 months ago by Stephen Feather

  • Show 2 more comments

4 Answers

Accepted Answer

We are getting the same error message when trying to submit a new version of an app that was successfully submitted in June to the app store.

This bundle is invalid. The application-identifier entitlement is not formatted correctly; it should contain your 10-character App ID Seed, followed by a dot, followed by your bundle identifier: xxxxxxxxxx.edu.umich.*

We are using a wild card ID and this time we are trying to submit using the "Publish" option built into the Titanium Studio eclipse app.

All submissions for apps from the University must be made through one office and so the entire project must be copied to a particular machine and built on it and then submitted from that machine. The challenge is that regular native xcode apps developed using Objective C are able to be submitted without getting this itunesconnect error message after uploading the binary - it appears that however Titanium Studio interacts with xcode to build the app is producing an xcode project that when built does not create an acceptable projec/binary that will be accepted by itunesconnect.

Has anyone else experienced this issue recently?

Any ideas what to try to fix this - I have read of two possible fixes:

  1. create an entitlements.plist file
  2. use a unique provisioning profile, not a wild-card ID

The appid in tiapp.xml should be similar to com.xxxx.appname and nothing else.

— answered 7 months ago by Stephen Feather
answer permalink
3 Comments
  • this should match the app id in the itunes connect/provisioning setup on developer.apple.com

    — commented 7 months ago by Stephen Feather

  • ok, crazy question. Are you sure its been signed by a production profile and not an adhoc?

    — commented 7 months ago by Stephen Feather

  • yeah sure I have signed by a Distribution Provisioning Profiles xxxxxxxxxxxxx.com.webdesignmtl.*

    — commented 7 months ago by wei huang

Hello Stephen, Yes the appid in tiapp.xml similar to com.xxxx.appname and nothing else. and yes it match the app id in the itunes connect provisioning setup too.

Did you try those two ways yet? create an entitlements.plist file use a unique provisioning profile, not a wild-card ID

— answered 6 months ago by wei huang
answer permalink
3 Comments
  • No I have not tried the two ideas yet - as I need to go to a separate office in the University to submit the app, I want to be able to have as much information as possible before going there. I would like to hear whether anyone has experienced this issue recently and what fix if any they came up with.

    it is frustrating that other native ios app xcode projects build correctly and can be submitted without an issue and the binary uploaded from an appcelerator project is not valid because of this "Invalid bundle" issue (see full error message in my post above)

    — commented 6 months ago by Laurence Kirchmeier

  • By using a unique provisioning profile AND NOT a wild-card provisioning profile, we were able to successfully upload and submit the binary for the app that we are updating.

    This appears to be a bug - I am going to submit a support ticket.

    — commented 6 months ago by Laurence Kirchmeier

  • ok. thx for keep us post.

    — commented 6 months ago by wei huang

Your Answer

Think you can help? Login to answer this question!