Bundle IDs with dots are being replaced with - and being rejected by the uploader

Getting Started Newbie Questions
#1

Hey ya,

I still can’t build for the AppStore past Corona Build: 2011.632.
I tried all builds up to the newest one.

Now build 2011.715 replaces a bundle identifier like com.blabla.appname with com-blabla-appname and iTunes Upload refuses it, since my bundle id is com.blabla.appname.

I had issues on around build .703 in which bundle IDs didn’t accepted dots, now they are just replaced.

Again, I just submitted building with 2011.632.

Anyone having the same issues?

Thanks. [import]uid: 10990 topic_id: 19860 reply_id: 319860[/import]

#2

This was a recent change we made because we were allowing illegal characters into the bundle id before. The new behavior mimics what Xcode does exactly.

If you need a specific bundle id, you may either use a fully qualified name in your provisioning profile (no wildcards) or explicitly declare the CFBundleIdentifier in your build.settings under the iphone->plist table.
[import]uid: 7563 topic_id: 19860 reply_id: 77078[/import]

#3

I tried explicitly declaring the CFBundleIdentifier and it also replaced the dots with - with uploader refusing it too. [import]uid: 10990 topic_id: 19860 reply_id: 77080[/import]

#4

Double check your build.settings and make sure you filled it out correctly. For example, the table ‘iphone’ must be all lower case.
[import]uid: 7563 topic_id: 19860 reply_id: 77085[/import]

#5

got the same issue a few days ago with 715 and was told to carry on

now I can see it was not a problem on my side probably [import]uid: 67641 topic_id: 19860 reply_id: 77184[/import]

#6

I’m having this same issue as well. Everything was working fine before. I set my Application Name to com.loqheart.cannoncat

and I removed the CFBundleIdentifier because another thread suggested removing it from the iphone plist table.

Now I keep getting 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: PK45W7W2MF.com-loqheart-cannoncat (-19054)

which looks related to karnak’s error.

I’m running build 715 as well.

Update:
I just built and submitted to the app store with build 689 while specifying the CFBundleIdentifier as com.loqheart.cannoncat. My provisioning profile Bundle ID is *. [import]uid: 27183 topic_id: 19860 reply_id: 77678[/import]

#7

This must be a build.settings issue (either the way people are formatting it, or including invalid paramaters perhaps?)

I have built 5 apps for device using team profile * id and other set profiles fine and submitted 1 app update and one new app to the app store with no issues with build 715 [import]uid: 84637 topic_id: 19860 reply_id: 77740[/import]

#8

I’ve been using Build 715 and submitted apps to the App-Store with no problems.
From what I can tell it’s most likely because I don’t use wildcard provisioning profiles.

I create one AppID for each of my apps and enter a fully qualified bundle ID. Yes, this does mean that you’ll have 2 provisioning profiles/app (developer + distribution), but it also means you don’t have to worry about typing in the correct bundle ID anywhere else. The build-process will take it from the provisioning profile.

A little more work in the iOS Provisioning Portal, but a lot less headache later… [import]uid: 70847 topic_id: 19860 reply_id: 77751[/import]

#9

I got a build working with 715 by creating a new App ID with a Bundle Seed ID using the Team ID and a fully qualified Bundle ID.

The confusing part is when building with the development provisioning profile, I get a warning about a “failed codesign verification. The signature was invalid, or it was not signed with an iPhone Distribution Certificate”. I hadn’t see this warning before, so I thought it was an error. Wasted a lot of time thinking I was doing something wrong. Why is this warning displayed now when it wasn’t displayed before? [import]uid: 27183 topic_id: 19860 reply_id: 77771[/import]

#10

We have noticed there seems to be a bug in Apple’s validation tool where a different validation failure gives you that error message “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: PK45W7W2MF.com.youcompany.foo (-19054)”

We think Apple uses this as the default fallback message if they don’t have the correct message for your case, which is not the correct thing. In addition, we discovered that you should NOT put the 10-character App ID seed in your CFBundleIdentifier even when developing natively in Xcode, so this is wrong too.

So it is possible you have some kind of validation failure and the error message is misleading you.
[import]uid: 7563 topic_id: 19860 reply_id: 77797[/import]

#11

@don
Yeah, whenever I build with a Development Certificate I get the following warning:

warning: Application failed codesign verification. 
The signature was invalid, or it was not signed with an 
iPhone Distribution Certificate. (-19011)

.

…but I’ve never paid much attention to it because it’s only a warning, and the warning is correct. I didn’t sign with a Distribution Certificate. I signed with a Development Certificate.

I guess they give you this warning to give you a heads-up just in case you intended to sign with a Distribution Certificate for later upload to iTunes Connect.
[import]uid: 70847 topic_id: 19860 reply_id: 77989[/import]

#12

Ingemar is right. I always when developing see this message too. But as @ingemar said above, this warning is still correct and ok because it knows as I know I am building WITHOUT the Distribution profile because I am not going (yet) upload/distribute this build for the App Store as well (just testing thing out, development time still). And so, after all the tests and codes, and then, I go to iTC to get my Distribution profile and like this be able to build for app store without see that WARNING MESSAGE any more and all is good.
Hope it let you with more info to do not worry about that @don.

PS: FYI, before I`ve never seen this message (when I started with Corona), but a couple of daily-builds ago looked like did this “warning” about the distribution profile pops-up! I just thought so: yes, looks like the Corona System is being even more smart. :slight_smile:
Cheers,
Rodrigo. [import]uid: 89165 topic_id: 19860 reply_id: 77998[/import]

#13

I have an App I first created a year ago without using Corona, and at the time I used a wildcard Bundle ID.

Now I’ve rewritten the game with Corona but can’t get a valid package together.

I’ve created a new App ID with a unique Bundle ID, and downloaded and installed the provisioning and distribution certificates, as mentioned above.

If I don’t specify the Bundle ID in the plist, the build is fine but I get a message from Application Loader that my bundle ID is different from the original. (The alpha numeric part is the same)

If I do specify the Bundle ID in build.settings, I get a Corona message saying the format is wrong.

I’m using daily build 704.

Any idea what I can do?? Really need to get my App updated. [import]uid: 52386 topic_id: 19860 reply_id: 80318[/import]

#14

In the iOS Provisioning Portal, have your checked if the Bundle Seed ID (10-char prefix) of your new App ID is the same as the old wildcard one?
[import]uid: 70847 topic_id: 19860 reply_id: 80335[/import]

#15

I have the same problem of @karnakgames and @shorty. @ingemar yes is the same id [import]uid: 45445 topic_id: 19860 reply_id: 80700[/import]

#16

I’ve got the same problem (again). I had this problem about a month ago and Ansca fixed it, but now it’s back in build 730, help!
[import]uid: 9046 topic_id: 19860 reply_id: 81340[/import]

#17

Hi, I’ve read this whole thread through and through and I tried some of the steps listed (Like putting CFBundleIdentifier in the build.settings file) but that has only made things worse.
Instead of fixing the problem its just made it worse…
Now when i remove CFBundleIdentifier from the build.settings folder I still get the same error and it doesn’t work in the application uploader.
Has anybody got any ideas about this?

I get this message from Corona:
“warning: Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate. (-19011)
Executable=/Users/matthewharrop/Desktop/GovernmentBingoB8.app/GovernmentBingoB8
codesign_wrapper-0.7.10: using Apple CA for profile evaluation”

This from Application uploader:
"This bundle is invalid. The application-identifier entitlements is not formatted correctly; it should contain your 10-character App ID seed, followed by a dot, followed by your bundle identifier: XXXXXXXX.appName

I’m running:
Version 2012.738 (2012.12.8) on Mac OSX Snow leopard.

EDIT: Sorry, i realised i’d missed a step. The new game is now in the approval process :smiley: [import]uid: 65237 topic_id: 19860 reply_id: 85146[/import]

#18

Hey @Mattew, would you mind telling us the exactly step that you missed?

Thanks,
Rodrigo. [import]uid: 89165 topic_id: 19860 reply_id: 85375[/import]

#19

Hi, sorry to the late reply to this, I forgot to tag it.
I’m actually having the same problem again. I am able to build i for distribution and upload it to the app store, but doing an ad hoc build doesn’t work.
When i attempt to install it on my iPad to test iTunes just refuses to do anything.

The step i missed was doing a profile for distribution, I was trying to upload it using an ad hoc profile.

Anybody got any ideas? [import]uid: 65237 topic_id: 19860 reply_id: 87075[/import]

#20

I still have problems.

I manage 16 Corona games (client games), so of course my build.settings is correct. The problem just persists after Corona 2011.632, meaning I can’t use many of the new features… [import]uid: 10990 topic_id: 19860 reply_id: 87924[/import]