I responded to this on another thread, but I’ll repeat it here with some more information.
We did some testing today and determined that the error saying the Bundle ID should contain the “10-character App ID Seed” is bogus and a bug in the Apple Validator code. What it’s telling you is the build ID specified in the distribution provisioning file does not match the CFBundleIdentifier in the APP package. This generally happens when you add your own Bundle Identifier to the Plist section in the build.settings file and you either have a wild-card bundle ID or a mis-match in the provisioning file.
If you don’t include a CFBundleIdentifier in the Plist section of the build.settings file, you shouldn’t run into this problem. Corona will create a CFBundleIdentifier field based on the bundle ID in the provision file used to sign the app. When you add a CFBundleIdentifier field in the build.settings file, you override the Corona generated field.
What seems to have changed in the lastest version of Xcode, is it now compares the bundle ID found in the provision file with the CFBundleIdentifier in the App package. If it finds any difference, it displays the “10-character App ID Seed” error.
If the bundle in your Provisioning file is fully qualified as in “com.company.appName”, that is what your CFBundleIdentifier will be in your app if you DON’T add the field to build.settings. If you add the field to build.settings, it must be exactly the same as in the provisioning file (including case sensitive).
If you use a wild-card bundle ID, as in “*”, your CFBundleIdentifier must be your app name. So if your app name is “Storyboard”, and you override the field in the build.settings file, it should be CFBundleIdentifier = “Storyboard”, or you will receive the error.
As an example, if your app name is “Storyboard”, here are some examples of how you need to set the CFBundleIdentifer field in the build.settings file to pass Apple’s Validator:
Provisioning Bundle ID / CFBundleIdentifier
[lua]com.company.Storyboard = com.company.Storyboard[/lua]
[lua]com.company.* = com.company.Storyboard[/lua]
[lua]com.* = com.Storyboard[/lua]
[lua]* = Storyboard[/lua]
The following is how Corona fills in CFBundleIdentifer if you DON’T add the field to build.settings;
[lua]com.company Storyboard = com.company.Storyboard[/lua]
[lua]com.company.* = com.company.Storyboard[/lua]
com.* = com.Storyboard[/lua]
[lua]* = Storyboard[/lua]
The bottom line is it’s best to leave the CFBundleIdentifier field out of the build.setting file and let Corona fill in the field for you.
As for what you should use as your Bundle Identifier in the provisioning file, use a fully qualified bundle name: e.g., com.company.AppName
If you want to use the same provisioning file for multiple apps, you can use a wild-card bundle name: e.g., com.company.*
Corona will substitute your app name for the “*” and the Apple Validator will be happy.
If you have an app already in the app store that was built with a CFBundleIdentifier in the build.settings file and now you can’t validate a updated version of the file, check your provisioning file Bundle ID. Your updated app must have a Bundle ID that matches the version in the App store and your only recourse may be to create a new provisioning file that matches the existing Bundle ID. In this case you should remove the CFBundleIdentifier field in build.settings file and let Corona create the Bundle ID for you.
Note: The above information was determined by creating a number of provision files and verifying the results when building Xcode projects and Corona projects. Let me know if you are seeing something different than what is described above. [import]uid: 7559 topic_id: 18931 reply_id: 73453[/import]
