bundle identifier issue trying to upload + some questions of clarification re build.settings

Getting Started Newbie Questions
#1

I’m trying to upload to Apple at the moment but having problems.

Q1 - I am getting: “Bundle Identifier: differs from prior bundle”. How can I solve this?

also

Q2 - What are the key attributes that need to matched when uploading? e.g. AppName, BundleID, Version? That is match between your corona app and what you have in itunes connect for your app?

Q3 - What should be used for the “Application Name” when you “build” in corona? Is this the App Name in iTunes Connect? (i.e. not the bundle name then, or the bundle name/app name?)

Q4 - The version name when you “build” in corona I assume has to match the version name for the “waiting for upload” version details you have in itunes connect?

Q5 - Title of app displayed under icon: Where in corona can you set this? I am updating an existing XCode application that had an Application Name that was a bit long, hence I used settings to make the Icon title/name to be “shorter” than the application name itself (using “bundle display name” in the Target Info settings in Xcode for the app). How do I do this in Corona so that after the version

Q6 - Is there a way to “Validate” your build as you can with XCode (where you create an archive and then use the Organizer under “archives” to click on “Validate”? Or can we assume this validation is just the same that you will get when you upload in Corona your application for real (via the appstore distribution profile)?

Q7 - More importantly than Q6, is there a way to truly test an AdHoc distribution. So really testing that given on my device I have V1 (built using Xcode) on it, that I can do a real AdHoc load V2 test and prove that this latest Corona build does update/overwrite/superseed it? i.e. I should be left with on one V2 app on my phone and not a V1 & V2. How would I do this?

Q8 - With Corona once I get past the validation type error (e.g. my Q1 above) for a true upload would it go live immediately potentially? That is, if you had iTunes connect set to automatically deploy, then straight after the Corona build/upload process would it go live immediately? i.e. just want to make sure I understand and don’t get caught out.
thanks

[import]uid: 140210 topic_id: 29766 reply_id: 329766[/import]

#2

PS - I’m currently using Version 2012.877 (2012.8.10) [import]uid: 140210 topic_id: 29766 reply_id: 119428[/import]

#3

PSS. My app ID uses a wildcard - whilst this is fine for an XCode development/deployment, is this a potential issue for a Corona deployment? Details of the wildcard approach are here: https://developer.apple.com/ios/manage/bundles/howto.action

If this were the issue then the next question is how to do my update in a fashion then that “replaces” the existing Xcode developed version of it? i.e. if I had to change the AppID from wildcard to fixed, hence I guess generating a new AppID? [import]uid: 140210 topic_id: 29766 reply_id: 119473[/import]

#4

Have put bundle identify in the build.settings file and now I am getting the following. Note that I opened up the created package and did confirm that the bundle identifier was in there correctly (i.e. in plist.settings)

warning: 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: . (-19054)

I’ve tried a couple of different formats for the App Name field when you Build in corona but it didn’t help with the above.

Ideas?
[import]uid: 140210 topic_id: 29766 reply_id: 119476[/import]

#5

@ansca - really need some help here - have purchased Corona but not much good if I can’t publish :slight_smile: [import]uid: 140210 topic_id: 29766 reply_id: 119544[/import]

#6

raised case 16564 (not sure of process so raised a case) [import]uid: 140210 topic_id: 29766 reply_id: 119559[/import]

#7

Update - have confirmed for myself the Corona upload issue relates to uploading to an IOS Application that was defined with a wildcard AppID as opposed to named. That is where when you create the App ID you just use a wildcard “*” for it. This is then reusable across multiple apps and save a little admin overhead. Separate named app id’s are only absolutely required when you want to use specific app features such as in-app purchases. So:

[A] NAMED APP ID - Worked

* Build.settings includes: CFBundleIdentifier = “com.mydomain.appname”,
* Corona Build Submission: Name = “appname”
* Corona Build Submission: Code Signing Identity = “iPhone Distribution: My Name (appname)”

[B] WILD CARD APP ID - ** CAN’T GET THIS TO WORK **

Try 1:
* Build.settings includes: CFBundleIdentifier = “com.mydomain.appname”,
* Corona Build Submission: Name = “appname”
* Corona Build Submission: Code Signing Identity = “iPhone Distribution: My Name (appstore)”

==> Fails on Corona build submission - Error = “warning: 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: QWERTYUIOP.appname (-19054)”

Try 2:
* Build.settings includes: CFBundleIdentifier = “appname”,
* Corona Build Submission: Name = “appname”
* Corona Build Submission: Code Signing Identity = “iPhone Distribution: My Name (appstore)”

==> Gets past Corona Build and saves the ZIP file to HDD. Then as soon as you click on “Upload to AppStore” you get the following message from the Application Loader. Error = “The Bundle ID appname defined in your Xcode Project does not match the Bundle ID that you entered for this app in the iTunes Connect com.mydomain.appname”

Question - Does Corona support me being able to update my existing iPhone app (developed in XCode) that used a wildcard application ID in it’s provisioning profile at all???

[import]uid: 140210 topic_id: 29766 reply_id: 119575[/import]

#8

PS. Also tried

[3] Uploading an Xcode based (non Corona) update to my app (with no enhancements) just to test (didn’t release it) and I did confirm that I could successfully do an update and in the outer Info.plist of the package Xcode build/uploaded I see:

CFBundleIdentifier
com.mydomain.appname
This is what I did with Corona in [1] and it didn’t work, whereas with XCode [3] it did work. Does this not imply a bug in Corona? Still trying to work out how I can get my enhancements (in my new V2 corona based version) to my existing Xcode V1 app…???
[import]uid: 140210 topic_id: 29766 reply_id: 119605[/import]

#9

Success!

Here’s what I did in case someone else gets stuck. I’ve just found some advice in the apple doco - the last section here: http://developer.apple.com/library/ios/#DOCUMENTATION/ToolsLanguages/Conceptual/DevPortalGuide/CreatingandConfiguringAppIDs/CreatingandConfiguringAppIDs.html

Updating Your App to Include APNS, iCloud, In-App Purchase, or Game Center Requires an Explicit App ID

As you develop, you might want to add features to your app. To support APNS, iCloud, In-App Purchase, or Game Center, you need an app signed with a provisioning profile that uses an explicit app ID. If you have an app that uses a wildcard app ID, you need to create a new app ID and then modify your provisioning profile.
To update your app ID: . . .

Identify your app’s current bundle ID in Xcode or iTunes Connect.

Create a new app ID in the App IDs area of the iOS Provisioning Portal with your app’s bundle ID search string.

Enable your app ID for APNS or iCloud (see “Configuring Your App ID for Apple Push Notification Service” or “Configuring Your App ID for iCloud”). Explicit app IDs are automatically enabled for In-App Purchase and Game Center.

Modify your provisioning profile to use the new explicit app ID.

I’ve gone through this process and now have successfully uploaded from Corona. It’s in the “Waiting for Review” state. So I hadn’t appreciated that a new app ID could be created, this associated with the provisioning profile (c.f. wildcard based one), and then the app uploaded with this provisioning profile in such a way that things link through to the same app version correctly.
[import]uid: 140210 topic_id: 29766 reply_id: 119741[/import]

#10

@greg886, wow, you’ve gone through quite a journey. Glad to hear you’ve got your issue sorted. Good luck with the Apple review process!

Naomi [import]uid: 67217 topic_id: 29766 reply_id: 119762[/import]

#11

thanks - now actually stuck with the V2 (corona based) update to my V1 (xcode based) not working successfully - have created Case 16688 for this one (https://developer.coronalabs.com/forum/2012/08/16/ad-hoc-deployment-steps-where-doco) [import]uid: 140210 topic_id: 29766 reply_id: 120174[/import]

#12

@ansca - really need some help here - have purchased Corona but not much good if I can’t publish :slight_smile: [import]uid: 140210 topic_id: 29766 reply_id: 119544[/import]

#13

raised case 16564 (not sure of process so raised a case) [import]uid: 140210 topic_id: 29766 reply_id: 119559[/import]

#14

Update - have confirmed for myself the Corona upload issue relates to uploading to an IOS Application that was defined with a wildcard AppID as opposed to named. That is where when you create the App ID you just use a wildcard “*” for it. This is then reusable across multiple apps and save a little admin overhead. Separate named app id’s are only absolutely required when you want to use specific app features such as in-app purchases. So:

[A] NAMED APP ID - Worked

* Build.settings includes: CFBundleIdentifier = “com.mydomain.appname”,
* Corona Build Submission: Name = “appname”
* Corona Build Submission: Code Signing Identity = “iPhone Distribution: My Name (appname)”

[B] WILD CARD APP ID - ** CAN’T GET THIS TO WORK **

Try 1:
* Build.settings includes: CFBundleIdentifier = “com.mydomain.appname”,
* Corona Build Submission: Name = “appname”
* Corona Build Submission: Code Signing Identity = “iPhone Distribution: My Name (appstore)”

==> Fails on Corona build submission - Error = “warning: 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: QWERTYUIOP.appname (-19054)”

Try 2:
* Build.settings includes: CFBundleIdentifier = “appname”,
* Corona Build Submission: Name = “appname”
* Corona Build Submission: Code Signing Identity = “iPhone Distribution: My Name (appstore)”

==> Gets past Corona Build and saves the ZIP file to HDD. Then as soon as you click on “Upload to AppStore” you get the following message from the Application Loader. Error = “The Bundle ID appname defined in your Xcode Project does not match the Bundle ID that you entered for this app in the iTunes Connect com.mydomain.appname”

Question - Does Corona support me being able to update my existing iPhone app (developed in XCode) that used a wildcard application ID in it’s provisioning profile at all???

[import]uid: 140210 topic_id: 29766 reply_id: 119575[/import]

#15

PS. Also tried

[3] Uploading an Xcode based (non Corona) update to my app (with no enhancements) just to test (didn’t release it) and I did confirm that I could successfully do an update and in the outer Info.plist of the package Xcode build/uploaded I see:

CFBundleIdentifier
com.mydomain.appname
This is what I did with Corona in [1] and it didn’t work, whereas with XCode [3] it did work. Does this not imply a bug in Corona? Still trying to work out how I can get my enhancements (in my new V2 corona based version) to my existing Xcode V1 app…???
[import]uid: 140210 topic_id: 29766 reply_id: 119605[/import]

#16

Success!

Here’s what I did in case someone else gets stuck. I’ve just found some advice in the apple doco - the last section here: http://developer.apple.com/library/ios/#DOCUMENTATION/ToolsLanguages/Conceptual/DevPortalGuide/CreatingandConfiguringAppIDs/CreatingandConfiguringAppIDs.html

Updating Your App to Include APNS, iCloud, In-App Purchase, or Game Center Requires an Explicit App ID

As you develop, you might want to add features to your app. To support APNS, iCloud, In-App Purchase, or Game Center, you need an app signed with a provisioning profile that uses an explicit app ID. If you have an app that uses a wildcard app ID, you need to create a new app ID and then modify your provisioning profile.
To update your app ID: . . .

Identify your app’s current bundle ID in Xcode or iTunes Connect.

Create a new app ID in the App IDs area of the iOS Provisioning Portal with your app’s bundle ID search string.

Enable your app ID for APNS or iCloud (see “Configuring Your App ID for Apple Push Notification Service” or “Configuring Your App ID for iCloud”). Explicit app IDs are automatically enabled for In-App Purchase and Game Center.

Modify your provisioning profile to use the new explicit app ID.

I’ve gone through this process and now have successfully uploaded from Corona. It’s in the “Waiting for Review” state. So I hadn’t appreciated that a new app ID could be created, this associated with the provisioning profile (c.f. wildcard based one), and then the app uploaded with this provisioning profile in such a way that things link through to the same app version correctly.
[import]uid: 140210 topic_id: 29766 reply_id: 119741[/import]

#17

@greg886, wow, you’ve gone through quite a journey. Glad to hear you’ve got your issue sorted. Good luck with the Apple review process!

Naomi [import]uid: 67217 topic_id: 29766 reply_id: 119762[/import]

#18

thanks - now actually stuck with the V2 (corona based) update to my V1 (xcode based) not working successfully - have created Case 16688 for this one (https://developer.coronalabs.com/forum/2012/08/16/ad-hoc-deployment-steps-where-doco) [import]uid: 140210 topic_id: 29766 reply_id: 120174[/import]