Unable to build for distribution

[BAMify]

We have previously built for distribution and successfully submitted 2 iOS apps, but we are now getting the following error (we are using latest daily build):

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: XXXXXXXXXX.AppName (-19054)

In our build.settings we have an appropriate bundle identifier:

CFBundleIdentifier = “com.bamify.appname”

If we remove the CFBundleIdentifier line, the build completes but on submission to itunes we get an error saying the bundle identifier differs from the reserved bundle identifier.

Just to note, previously we have built from a different OS X machine (we have deauthorised and authorised on new computer) - I’m not sure if this is related to the issue?

Any ideas what is causing this? We would really like to get this app submitted as soon as possible!

Thanks,

Bryn
[import]uid: 62042 topic_id: 18384 reply_id: 318384[/import]

[peach_pellen]

Hey Bryn,

What build of Corona are you currently using?

Peach [import]uid: 52491 topic_id: 18384 reply_id: 70495[/import]

[BAMify]

Hi Peach

Well, we were trying to build with 2011.694, but I’ve just updated to 2011.696 and we get exactly the same result.

I noticed the following warnings on app build, I’m not sure if they’re related to the issue:

2011-11-29 23:37:44.635 Corona Simulator[548:903] WARNING: Could not find
certificate for identity (iPhone Developer: Bryn Jones (XXXXXXXXX)) whose
user id is: XXXXXXXXX
2011-11-29 23:37:44.637 Corona Simulator[548:903] WARNING: Could not find
certificate for identity (iPhone Developer: Michael Griffiths (XXXXXXXXX))
whose user id is: XXXXXXXXX

If you can help further that would be really appreciated, thanks!

Bryn [import]uid: 62042 topic_id: 18384 reply_id: 70539[/import]

[peach_pellen]

This sounds like a certificate issue not a Corona issue. I’ve personally used build .689 for a few builds lately so can confirm it works, so does the last stable .591 if you would like to try building using that.

However, because this is the only report I’ve seen, it appears far more likely there has been issue in installing your certificates correctly in the new machine - you should open keychain access and see what you have there, if it matches the previous computer, etc.

Can you do that and let me know, please?

Peach [import]uid: 52491 topic_id: 18384 reply_id: 70544[/import]

[BAMify]

Okay, thanks, I will try check when I have access to both machines later today.

A question - is it possible to keep both machines authorised with Corona, and not have to deauthorise all the time? It’s just it’s not always convenient to keep switching.

[Edit] - Another couple of questions:

When we created the distribution certificate, we used the same account as on the other machine to create the request. Is that okay, or should we use a different account for different machines?

What version of Xcode is recommended? As we’re running 3 I think on this machine .

Thanks

Bryn [import]uid: 62042 topic_id: 18384 reply_id: 70573[/import]

[BAMify]

Ok, another update

I’ve upgraded Xcode to version 4.2 - this appears to have made no difference at all.

I have also deleted and recreated (several times) the distribution profile, and also my own personal developer profile. Xcode reports no problems with either.

When I build now, I still see warnings in the terminal for the other developer, but not for myself. I have the other developer’s certificate on my machine, but not his keys - but is this necessary, given that Xcode says all is well, and the distribution profile was created by my user?

If the above is necessary, what are the steps - simply export both private and public keys from the other machine?

Any other advice or recommendations that you could offer greatly appreciated. If you could also respond to my question regarding authorization on multiple machines that would be cool too

Bryn
[import]uid: 62042 topic_id: 18384 reply_id: 70690[/import]

[peach_pellen]

Hey again,

First up - you can run Corona on two machines and have it authorized on both at once. If you are having issues with that it means you have 2 authorized already. You can contact support and get a deauthorize to fix this. Use this link; http://developer.anscamobile.com/forms/support

The distribution certificate should be the same on all machines. (As should the developer certificate, if installed.) You should also be sure you’ve downloaded the world wide developer agreement from Apple. (Available on certificate pages in the iOS developer portal.)

For Xcode, version 4.2 is correct, it is the latest non-beta. (Which is what you want.)

From the sounds of things the keys are the problem, yes - export keys, import them to your machine and that should fix the issues.

Peach

[import]uid: 52491 topic_id: 18384 reply_id: 70717[/import]

[BAMify]

Thanks Peach. An update for you - we’ve still had no success building the app for distribution. In fact, we’ve even tried to build it on the other machine with no success, and gone through the process of certificates and provisioning countless times

Are there any other things that might cause this issue? We (both Mike and I) are currently pulling our hair out over this as we’re keen to release the game before the holidays.

Thanks,

Bryn [import]uid: 62042 topic_id: 18384 reply_id: 71060[/import]

[BAMify]

App is SUBMITTED

To be honest, I’m not sure what changed - i think maybe we selected the wrong App ID in the distribution provisioning profile, as we’d created 2 with our game’s name.

Lesson is that first assumptions (new machine, not configured correctly) aren’t always correct!

Thanks for the help anyways

Bryn [import]uid: 62042 topic_id: 18384 reply_id: 71163[/import]

[peach_pellen]

I am glad it all worked out OK and appeared to be an App ID issue - thanks for updating and good luck in the review process!

Peach [import]uid: 52491 topic_id: 18384 reply_id: 71191[/import]