Actually, yea - the last few times I tried the bundle ID was correct (co.moonbeam.blabberboxchristmas) but Apple states it was wrong -
[import]uid: 9046 topic_id: 18931 reply_id: 73534[/import]
@MBD, you should file a bug with Apple about that. [import]uid: 7559 topic_id: 18931 reply_id: 73537[/import]
How would this be Apple’s fault? When I go back to build 689 of Corona the app builds and submits fine, but anything higher, and using the fully qualified bundle name the build itself (from Corona) doesn’t work.
Just trying to figure this all out, I want to be on the latest release of Corona but had to stick back on 689 because of this which means I can’t do certain things.
[import]uid: 9046 topic_id: 18931 reply_id: 73540[/import]
@MPD,
Can you send me the info.plist for a build done with 689 and one with the latest Corona build? I didn’t think there were any changes that would cause this. You can email it to tom at anscamobile dot com.
Update: What version of Xcode are you using?
Thanks,
Tom [import]uid: 7559 topic_id: 18931 reply_id: 73543[/import]
Tom, I think there is a key point for us here and that is what is deemed to be a wildcard provisioning profile - in our case we are talking about an asterisk only, but you talk about a syntax like com.bamify.* …I don’t think this is particularly clear from the build guide in your docs and maybe that needs to be made more so.
So, is there maybe a problem in how corona may handle the build cases like ours, with a true wildcard provisioning profile? [import]uid: 62042 topic_id: 18931 reply_id: 73571[/import]
The wild card bundle ID is something that Apple defined and is not a Corona feature. If you build an app and let Corona handle the App Name and CFBundleIdentifier (without overriding the fields), you should have no problem with the build or uploading to Apple. When you try to override the fields, that is when we get into these problems. Creating a provisioning file with just “*” or “com.*” or “com.company.AppName” will work correctly UNLESS you try to override the CFBundleIdentifier field in the build.settings file, and you don’t match it exactly. Corona will create the proper bundle ID if you let it.
I will update the Corona documentation to say you should AVOID adding your own CFBundleIdentifier in the build.setting file. It’s okay to add a CFBundleDisplayName but you should avoid changing the Bundle name. I will also mentioned that it’s best to have fully qualified bundle IDs (no wild cards) in the provisioning file. This will be needed if you ever want to do In-App purchases, push notifications, or iCloud.
If you were doing an Xcode project, you would have to enter the bundle ID manually and you would not be able to code sign the app if the Bundle ID in your provisioning profile didn’t match.
Corona makes it easier to build and codesign, but trying to override the fields may cause problems like this. [import]uid: 7559 topic_id: 18931 reply_id: 73577[/import]
@MPD,
Your issue isn’t with the CFBundleIdentifier, but a mangled BundleName caused by using the bundle ID as your Application Name. We never expected someone to change the Application Name to that of their full bundle ID. The change we made after build 689 would truncate the name if it found a dot. [import]uid: 7559 topic_id: 18931 reply_id: 73584[/import]
I would accept that , had I not tried just using a name in the app name field as well with the bundle id in my build.settings file. It would build from the Corona side, but wouldn’t submit to Apple.
So what to do? [import]uid: 9046 topic_id: 18931 reply_id: 73588[/import]
@MPD,
We are looking into a fix that would allow a dot in the Application Name. [import]uid: 7559 topic_id: 18931 reply_id: 73597[/import]
@MPD,
Daily Build 706 now allows extra characters in the Application Name field, which should solve your problem.
We don’t recommend using characters beyond the standard alphanumeric, space and dash. It’s also recommended that you use the project name as it’s populated in the Application Name field instead of overriding it with your own name.
If you need to change the app name that is displayed on the device, you can add a CFBundleDisplayName in the plist section of the build.settings file. There is no restriction as to what you can put in this field.
[import]uid: 7559 topic_id: 18931 reply_id: 73792[/import]
Awesome, thanks for being so quick to put that back 
[import]uid: 9046 topic_id: 18931 reply_id: 73797[/import]
Tom, this is back again in build 730. I can no longer put in my com.appname.moonbeam, etc… [import]uid: 9046 topic_id: 18931 reply_id: 81342[/import]