To my knowledge, nothing has changed in Corona that would affect the bundle ID error you're seeing. Build 689 should work the same as build 703.

We did some testing today and determine 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.

Jonathan is correct in telling you to not add this to the build.settings file UNLESS you want to match exactly when is in the Distribution Provisioning file. If you leave the CFBundleIdentifier out of the Plist section, Corona will fill in the field for you from the provisioning file that you specify to sign the app. If you try to override it, and you're wrong, the Validator will catch it and display the error you're seeing. The main cause seems to be with provisioning files with wild-card bundle IDs.

We believe the latest version of Xcode (4.2) has an updated Validator program that compares the CFBundleID against the provisioning file Bundle ID and displays this error.

@MDB: The difference between older builds and newer builds is, as Tom mentioned, the fact that Xcode 4.2 has a new validation tool that will throw errors if there are problems with the bundle ID. It seems it is very sensitive, and can even throw the error even when you match it exactly and you're using a certain type of provisioning profile.

Your best bet is to just let Corona handle the bundle ID stuff and not worry about setting it yourself in the build.settings file.

Hello, I just upgraded from 4.2 to xcode 4.3, using build 767, and now I am suddenly getting this error, which wasn't there before.

I have never inlcuded CFbundleId in my build.settings, so what else could cause this problem?

I am getting an armv6 error as well as this one. I have ready that the cfbundleid error can be a generic error, so it might go away if I figure out what is causing the armv6 problem.

Some other apps and sample are building fine. I am just now getting this new issue when trying to simply re-build some of my previously approved apps (unchanged) with the newer corona build/xcode so they will work properly on the new iPad.

Thanks Tom. I will keep digging... here is my current build.settings file for this project.. it gives the armv6 error in both 4.2 and 4.3, but didnt previously in 4.1x:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

settings =
{
        orientation =
        {
            default = "portrait",
            supported = {"portrait", "portraitUpsideDown" }
        },
 
        iphone =
        {
                plist =
                {
                        UIPrerenderedIcon = true,
                        CFBundleDisplayName = "myAppName",
                        UIApplicationExitsOnSuspend = true,
                        CFBundleIconFile = "Icon.png",
                        CFBundleIconFiles = 
                        {
                                "Icon.png" , 
                                "Icon@2x.png" , 
                                "Icon-72.png" , 
                                "Icon-Small-50.png" , 
                                "Icon-Small.png" , 
                                "Icon-Small@2x.png"
                        },
                        UIAppFonts = 
                        {
                        
                        }
 
                   }
        }
}

I have used this exact build.settings successfully on a different project with 4.2 and 4.3, so I believe the problem is elsewhere in the code... but I have no idea where to start.

Tom, Thanks again for your help!

By app name, do you mean the DisplayName defined in build settings, or the app name I give it when I build in the corona dialog?

Here's what I did, but I still get the same armv6 error:

• renamed build.settings to __build.settings
• tried a different mobileprovision (distribution this time) that was previously successful
• eliminated an underscore from my app name in the corona build dialog

All of these didnt help... could there be some deprecated code that requires armv6?

OK, I will try that... using 2012.767

Relatively new to Corona, just got one-star "app is useless!" review from irate iPad 3 owner. While trying to quickly resolve retina issue, got first-ever 'invalid bundle' error ...

Setup WAS: 10.6.8, Xcode 3.2.5, Corona 2011.591
Setup NOW: 10.6.8, Xcode 4.2, Corona 2012.767

Testing on iPad 1 & iPad 3 running iOS 5.1, development build runs fine. Distrib builds fine.

I activated CFBundleIdentifier line in my build.settings file for final build and got 'invalid bundle' error. Sounds like I can delete that line and submit.

First, I'd like to confirm 2 things:

1) Per a post recommendation, to make Xcode 4.2 work with iOS 5.1, I added xcode_431_lion.dmg's version.plist and DeviceSupport/5.1 & Latest(alias) files to Xcode 4.2 folders.

2) Corona 2012.767 seems to hang after any build; amber clock animation runs until you quit or relaunch.

Is dmg-file plucking fine; amber-clock normal; just delete CFBunID line and upload?

I greatly appreciate any feedback you can give. Thanks very much. Best, Lynne

lbolduc, I have a Macbook Pro 2.66ghz... I was a little skeptical about putting Lion on just for the sake of updating xcode to 4.3, but it worked out fine on my machine. Its worth the $30 to get it done and over with.

When you update to xCode 4.3:

1. Tell the installer YES to remove the old xCode.
2. Launch xCode once and let it finish its first run.
3. Look up xcode-select on google or here, to point corona in the right direction for the newly installed xCode app in your Apps folder.

Also be sure to do housekeeping and clean out old versions of the app from your project folder. Test build with the sample apps too if you you are ever unsure whether the problem is in your app vs corona/os/xcode.

Best of luck, and hope that helps

Glad to help... I wont digress into the silly consumer features of Lion... it's easy enough to ignore them... and you can change the scrollbar back to normal in the System Prefs under Mouse.

Cheers!