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

_RSCdev · February 19, 2012, 2:30pm

WOW…so it should be resolved asap Ansca Team!

HELP US!
Thanks,
[import]uid: 89165 topic_id: 19860 reply_id: 87930[/import]

karnakgames · February 19, 2012, 2:31pm

Ok, it just doesn’t work at all.

I’ll have to fallback to 632 AGAIN, and take off Game Center…

Why don’t you make the build process as efficient as it is in 632 and earlier? [import]uid: 10990 topic_id: 19860 reply_id: 87931[/import]

Danny · February 19, 2012, 3:13pm

What version of xcode are you running ? [import]uid: 84637 topic_id: 19860 reply_id: 87943[/import]

MatthewCharlesHarrop · February 20, 2012, 2:14am

I am running 4.2 build 4C199
The bizarre thing is that i can build a release candidate that works fine, but when i come to build an ad Hoc release I get that failure and am unable to install it upon my devices [import]uid: 65237 topic_id: 19860 reply_id: 88062[/import]

peach_pellen · February 20, 2012, 11:35pm

Matthew, I see that you say you are trying to install via iTunes.

Have you tried doing so via Xcode? In some scenarios this can (and does) make a difference.

Would you be able to try that and let me know, please?

Steps to install via Xcode rather than iTunes:

Plug in device
Open Xcode
Go Organizer (CMD+Shift+2)
Click your device on left, if there’s a button to “enable for development” (or anything similar) click it and follow steps.
Drag and drop app file onto your device on the left sidebar. [import]uid: 52491 topic_id: 19860 reply_id: 88307[/import]

MatthewCharlesHarrop · February 21, 2012, 1:17am

Ahhhh, thats got it! Just seems my iTunes is messed up.
Thanks Peach

So when can we see this problem being addressed? (With the dots being replaced with dashes) [import]uid: 65237 topic_id: 19860 reply_id: 88329[/import]

conor1 · March 9, 2012, 7:42am

I’m having the same problem, and it appears on apps that I previously built (February 27) and have not been modified since. Same code as above. Nothing has changed my side, I’m using macincloud and same version of corona on their server. I’m building using the files and provisioning profile that have resided on the macincloud server since that date.
So, surely the error is being generated either on Corona server, or by Apple when Corona server talks to apple server???

I’m stuck unable to test my apps on ipad. [import]uid: 120570 topic_id: 19860 reply_id: 92183[/import]

peach_pellen · March 9, 2012, 11:19pm

conor, do you need to include your bundle ID in build.settings? If it isn’t necessary then simply remove it. (I never include it unless doing IAP/GC.) [import]uid: 52491 topic_id: 19860 reply_id: 92326[/import]

conor1 · March 10, 2012, 12:01am

Peach, no bundleID in build.settings

To clarify.
I have 3 prototype projects all of which built successfully Feb 26-28. All ran on ipad happily.
2 of the projects don’t even have a build.settings file.

Yesterday I attempted to rebuild one which had since changed and got the failure detailed above. So then I decided to rebuild one of the older ones, still on the macinloud, unchanged since last build. This fails too, despite there being no difference.

As an additional test this morning, I created a new provisioning profile for the change project, and still I get the failure.

I’m happy to supply the code and provisioning profile for either the changed or unchanged project. [import]uid: 120570 topic_id: 19860 reply_id: 92352[/import]

ewing · March 10, 2012, 1:12am

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]

conor1 · March 10, 2012, 1:35am

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]

ewing · March 10, 2012, 1:53am

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]

conor1 · March 10, 2012, 2:49am

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]

conor1 · March 10, 2012, 2:56am

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]

ewing · March 10, 2012, 4:04am

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]

conor1 · March 10, 2012, 5:38am

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

ewing · March 10, 2012, 11:48am

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

conor1 · March 10, 2012, 11:49pm

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

ewing · March 12, 2012, 11:43am

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]

washing · May 10, 2012, 12:35am

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]