Anyone else getting this message when building for distribution?
warning: This bundle is invalid. The application-identifier entitlement is not formatted correctly; it should contain your 10-character App ID Seed
I’ve been trying all day to get an update posted for our latest app (just build and signed the same way a week ago) but it won’t work. I get this message over and over.
I’m on the latest stable release of Corona SDK.
[import]uid: 9046 topic_id: 19023 reply_id: 319023[/import]
Just a little more insight into this issue.
I always use CFBundleIdentifier=“com.mycompany.appname”, in my build.settings files. I have for 10 apps now using Corona - always works fine.
When I build, in the app name prompt box I put the bundle ID - which is “appname”, with me so far?
So starting today when I build, the error is (in it’s entirety)
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: 7K3F8T0T3D.co (-19054)
co is the first part of my bundle ID (co.moonbeam.appname)
I can’t help but think this is happening on the built itself when sent away to Corona…
[import]uid: 9046 topic_id: 19023 reply_id: 73331[/import]
As another note - I FINALLY got my build submitted to Apple, but I had to go ALLLLLLLL the way back to version 689 of Corona SDK to get it done.
Ansca - please fix this asap.
[import]uid: 9046 topic_id: 19023 reply_id: 73387[/import]
Remove the CFBundleIdentifier from build.settings, it’s not needed. Corona will use the bundle id associated with the provisioning profile. It has never been required to add it into build.settings.
So please try the latest builds again, because it should work. Someone else reported the same problem and removing that line from their build.settings fixed everything. [import]uid: 52430 topic_id: 19023 reply_id: 73422[/import]
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.
[import]uid: 7559 topic_id: 19023 reply_id: 73442[/import]
The above statements are not true in this case I’m afraid.
a) I downloaded the latest Xcode before contacting you guys and it didn’t help.
b) I’ve used the bundle ID in my build.settings file since I started with Corona, it has never been an issue. I always match exactly (copy and paste) what is on my Apple app page for a bundle ID.
[import]uid: 9046 topic_id: 19023 reply_id: 73499[/import]
@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. [import]uid: 52430 topic_id: 19023 reply_id: 73594[/import]
Textmate corona LUA bundle proposes a build.settings template like
-- The following are typical values for a landscape-mode app. Edit at will!
-- Supported values for orientation: portrait, portraitUpsideDown, landscapeLeft, landscapeRight
-- Boolean plist properties take a Lua-style true/false setting
-- Don't forget to set CFBundleIdentifier to something meaningful!
settings = {
orientation = {
default = "landscapeRight",
supported = { "landscapeLeft", "landscapeRight" }
},
iphone = {
plist = {
UIStatusBarHidden = true, -- true or false
CFBundleShortVersionString = "1.0",
CFBundleVersion = "1.0.0",
CFBundleIdentifier = "com.company.app",
UIPrerenderedIcon = true, -- set to false if you want the gradient overlay
UIApplicationExitsOnSuspend = true,
}
},
androidPermissions = {
"android.permission.INTERNET",
},
} I had encountered this error also because I thought it was a mandatory. [import]uid: 5578 topic_id: 19023 reply_id: 85532[/import]
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? [import]uid: 42286 topic_id: 19023 reply_id: 95731[/import]
The problem could be in your provisioning file, a build.settings problem or something is wrong in the file name. You didn’t post the entire message so it’s hard to say. Try building one of the sample apps and see if you get the same error.
I’ve never heard of this problem caused by upgrading from 4.2 to 4.3. [import]uid: 7559 topic_id: 19023 reply_id: 95743[/import]
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. [import]uid: 42286 topic_id: 19023 reply_id: 95750[/import]
The ARM6 error message means something is wrong with your build.settings file (e.g., plist settings). If you never built this app with Xcode 4.2 before, this may be why you are seeing the error because Apple is now more critical in what they allow in the build process.
Apple’s error messages are generally wrong about what the problem is but do mean there is something wrong somewhere, which is generally in the build.settings file. [import]uid: 7559 topic_id: 19023 reply_id: 95754[/import]
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:
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. [import]uid: 42286 topic_id: 19023 reply_id: 95767[/import]
Here are some thoughts.
Try building the app without the build.settings file (rename it) and see if that passes.
What is the project name you are trying to build? We’ve had problems with that in the past.
Are the apps that work using the same provisioning file as the one that fails? Are you building for developer or distribution? Try a different one (if you can). [import]uid: 7559 topic_id: 19023 reply_id: 95775[/import]
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?
[import]uid: 42286 topic_id: 19023 reply_id: 95782[/import]
What corona build are you using?
Do you see any errors or warnings in the terminal when you do a build?
Are you requiring any libraries and if so, make sure there are no issue with the case in the file names.
Are any of your libraries in subdirectories?
I think the ARMV6 and invalid CFBundleIdentifier are bogus errors from Apple but something else is wrong.
You might trying naming your app “test” in the Corona build window and rename your config.lua file to remove it as a possible problem.
[import]uid: 7559 topic_id: 19023 reply_id: 95795[/import]
OK, I will try that… using 2012.767 [import]uid: 42286 topic_id: 19023 reply_id: 95812[/import]
Chiming in to report I resolved both of my issues. For those who might be searching for help with these errors, I’ll list them here:
warning: iPhone/iPod Touch: application executable is missing a required architecture. At least one of the following architecture(s) must be present: armv6 (-19033)
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)
It turns out the problem was a housekeeping issue… I had an old copy of the .app and .zip from the previous version sitting inside my project folder along with main.lua, etc. Removing the old .app and .zip files from the main project folder allowed the app to build successfully.
Hope this helps someone in the future.
[import]uid: 42286 topic_id: 19023 reply_id: 96313[/import]
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:
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.
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
[import]uid: 11631 topic_id: 19023 reply_id: 97329[/import]
The invalid bundle error will occur if you try to include the CFBundleIdentifier in the build.settings file and you get it wrong. The recent versions of Xcode are now very strict on making sure it matches what you set in your provisioning profile.
As far as extracting the Xcode tools and building for 5.1 using Xcode 4.2, that is untested and unsupported by Ansca. Apple requires Xcode 4.3 and Lion to build for iOS 5.1 and that is the only configuration that is officially supported.
The “amber-clock” after a build is normal and indicates that the simulator has been suspended. You can relaunch or CMD+down arrow to resume.
[import]uid: 7559 topic_id: 19023 reply_id: 97339[/import]