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

Getting Started Newbie Questions
#30

We need you to be very detailed and very exact about what you are doing.

Yes, the newer builds change the algorithm on how bundle ids are automatically created when they contain illegal characters.

But specifying CFBundleIdentifier will always bypass this. If you have an existing bundle id that you must continue to use, you must set this correctly. If it is not working, then you are setting it incorrectly in your build.settings or there is a bug in Corona. However, we run an automated test daily that specifies an exact CFBundleIdentifier in build.settings so we can run Game Center tests so I consider it less likely this is a Corona bug.
Things you must do:

  • Open up your old .app bundle and look at the Info.plist and see what the bundle identifier is set to. It should be something like com.yourcompany.yourapp
  • Verify this matches what is on iTunes Connect
  • Using the newest Corona, add this bundle identifier to your build.settings and check the Info.plist to see what gets written. This should be com.yourcompany.yourapp

If you do not see the string overridden, then verify you filled out your build.settings correctly. Try building a Hello World app with the bundle identifier set and reverify what gets written.

Also try the GCTapper (Game Center example). I believe it also has an overridden bundle identifier so it can talk to Apple’s test board. Verify the bundle identifier that got written to its info.plist and see if you can view the Apple leaderboards.

[import]uid: 7563 topic_id: 19860 reply_id: 92365[/import]

#31

I suspect we have 2 different problems being described here, but showing the same symptom. The original poster has an issue with bundle identifier.
My problem isn’t with bundle identifier, because I haven’t introduced one yet (I’m months from submitting to appstore).

My problem is a change somewhere in the build process since Feb 28. Same code, same build, same provisioning profile, different results 2 weeks later.

Further clarification
Corona build on macincloud is 2011.591 [import]uid: 120570 topic_id: 19860 reply_id: 92367[/import]

#32

We have no common baseline to understand your problem and we don’t know how to independently reproduce your problem, so you are going to have to take these annoying baby steps I described so we can figure out what’s going on. You should do everything I just said to do above. But you might shuffle the order and start with the Hello World and GCTapper examples.

[import]uid: 7563 topic_id: 19860 reply_id: 92368[/import]

#33

I think I need to give further clarification.
This is NOT about bundleID.
Perhaps I’m in the wrong thread but I got the same symptom as original poster.

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

I can’t do the baby steps with bundle identifier because I’m not using one. I did check the info.plist, and the bundleID is correct, matches the provisioning profile. Inserted automatically by Corona I guess.

My info.plist is below.
Let me emphasis again that code that ran successfully on Feb 26 fails to pass Apple’s validation. This is despite the fact that the code hasn’t changed and I’m using same of everything.

<?xml version="1.0" encoding="UTF-8"?>



BuildMachineOSBuild
10J869
CFBundleDevelopmentRegion
en
CFBundleDisplayName
citymaze
CFBundleExecutable
citymaze
CFBundleIdentifier
com.apptoonz.citymaze
CFBundleInfoDictionaryVersion
6.0
CFBundleName
citymaze
CFBundlePackageType
APPL
CFBundleResourceSpecification
ResourceRules.plist
CFBundleSupportedPlatforms

iPhoneOS

CFBundleVersion
1.0
DTCompiler
com.apple.compilers.llvm.clang.1_0
DTPlatformBuild
8F192
DTPlatformName
iphoneos
DTPlatformVersion
4.3
DTSDKBuild
8F191m
DTSDKName
iphoneos4.3
DTXcode
0400
DTXcodeBuild
4A1006
LSRequiresIPhoneOS

MinimumOSVersion
3.1
NSMainNibFile
MainWindow
NSMainNibFile~ipad
MainWindow-iPad
UIApplicationExitsOnSuspend

UIDeviceFamily

1
2

UIStatusBarStyle
UIStatusBarStyleBlackTranslucent

[import]uid: 120570 topic_id: 19860 reply_id: 92372[/import]

#34

Further update.

Just did helloworld, new provisioning profile. Same result.
Corona build on macincloud is 2011.591

What has changed at server level since Feb 26? [import]uid: 120570 topic_id: 19860 reply_id: 92374[/import]

#35

2011.591 is really old. The current stable is 704. We can’t really support that.

We noticed Apple changed something about their code signing process around iOS 5.0. Users who did not upgrade to the latest Xcode were getting similar failures like you.

[import]uid: 7563 topic_id: 19860 reply_id: 92382[/import]

#36

macinacloud has xcode 4.2.1
I’ll ask about 4.3 [import]uid: 120570 topic_id: 19860 reply_id: 92388[/import]

#37

2011.591 is probably too old to work with Xcode 4.2.1. [import]uid: 7563 topic_id: 19860 reply_id: 92428[/import]

#38

Got 2011.704 installed, but still the same error. xcode 4.2.1. [import]uid: 120570 topic_id: 19860 reply_id: 92525[/import]

#39

You can do the baby steps. You just add the CFBundleIdentifier to your build.settings. Please see the Game Center sample code in the latest daily builds of Corona as an example.

[import]uid: 7563 topic_id: 19860 reply_id: 92836[/import]

#40

Hi Karnak,
do you mind sharing what XCode & is it Snow leopard or lion did you use for SDK 2011.632? [import]uid: 89468 topic_id: 19860 reply_id: 105851[/import]

#41

Hi, i have the same problem here, with build 828 :frowning:
i wanted to update my app to retina display support.

the error i get with a classic build: Bundle identifier: com-magicwhale-bagatelle differs from prior bundle identifier: com.magicwhale.bagatelle

So it’s COrona changing the . to - .

when i try to add CFBundleIdentifier = “com.magicwhale.bagatelle”, to my build.settings, i got another error telling me that the bundle ID 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: xxxxxxxxx.com.magicwhale.bagatelle (-19054)

i even tried to change the bundle id within the built, but then apple tells me it’s not a valid build (modified, not signed)

So, because i can’t change the bundleid of my app, i’m locked :frowning:

many people have old bundle ids with dots in it, can’t you just change it in the builds so that you are warned that you have invalid characters in your bundle id, but DON’T change them?

Howe the others have resolved this? [import]uid: 44010 topic_id: 19860 reply_id: 110420[/import]

#42

Hi Raphael,

It’s been a while since I resolved this issue, but I believe I had to create a new App ID for Cannon Cat. There wasn’t anything I could do inside of my build.settings that made a difference. And looking at the history of my provisioning portal it’s littered with failed app ids like:

com.loqheart.cannoncat - this was the original
com.loqheart.cannoncat.app
com.loqheart.cannoncat.001
com.loqheart.cannoncat.full - this is the one I’m currently using.
[import]uid: 27183 topic_id: 19860 reply_id: 111199[/import]

#43

Hi DOn :slight_smile:
so you are using a name with dots and don’t have problems publishing with the latests daily builds?
When you are building you app in corona, you put com.loqheart.cannoncat.full as the name of the app? [import]uid: 44010 topic_id: 19860 reply_id: 111291[/import]

#44

Yes, I’m using 825 and com.loqheart.cannoncat.full without any issues. [import]uid: 27183 topic_id: 19860 reply_id: 111292[/import]

#45

that’s strange… your dots are not replaced with “-”? [import]uid: 44010 topic_id: 19860 reply_id: 111293[/import]

#46

I was having the same problem, i was making a free version of my apps and i forget to change the CFBundleIdentifier in build.settings [import]uid: 113117 topic_id: 19860 reply_id: 111989[/import]

#47

noeguer-> what is the exact syntax of your CFBundleIdentifier in build.settings?
i have tried with this, but another error pops up when i try to upload :confused: [import]uid: 44010 topic_id: 19860 reply_id: 112274[/import]

#48

problem resolved :slight_smile:
tried to create a new distribution profile, and it works like a charm :slight_smile: [import]uid: 44010 topic_id: 19860 reply_id: 112360[/import]

#49

previously everything works fine on builds 786 for me. now 786 or 840 is not working. [import]uid: 89468 topic_id: 19860 reply_id: 115058[/import]