CODEWITHSUNDEEP
iosxcodeapp-store
Julian
Julian

Reputation: 9130

Tips and gotchas when developing with multiple Apple IDs

I'm in charge of developing and submitting the apps to the app store as the clients have sent us their apple logins. As far as developing the apps, that's been OK (I haven't submitted any yet) but in the next week I will need to submit at least three, all with different Apple IDs.

I've removed the Xcode password from the keychain and synced my certificates to the second Apple ID I have. Oh god, the mess it made with my keys, and profiles. When I did this with my own Apple Id (Xcode 3) I had to do the whole thing manually and could name keys, etc like I wanted. I entered the second Apple Id (Xcode 4) and now Xcode want's to manage everything for me. I like this but it created the keys and profiles with some stupid names. It makes it very difficult for me to sign apps with one or the other and also to backup one client's keys and not confuse them with mine. I'm afraid to enter the third Apple Id because I know the mess will be impossible to handle.

I'm open to tips, gotchas to look out for when working with multiple Apple IDs so that I can know "how it's done". And also, any other things along the way that I might encounter in the submission progress.

Upvotes: 1

Views: 311

Answers (1)

Jim
Jim

Reputation: 73936

This is much easier if you use a separate user account on OS X for each client.

If you use one shared account for everything, then there shouldn't be any conflict if you only have one developer key and use separate bundle IDs for each application. The signing works backwards from the bundle ID - from the bundle ID it finds the correct provisioning profile, and from the provisioning profile it finds the correct distribution key.

Upvotes: 1

Related Questions