Signing identiy and keychain

[karl]

This is kind of an old thread now, but I ran into it for the first time yesterday after having to restore my iphone (2.2.1 fyi). Anyway, the fix of not having multiple certificates in the keychain access was what fixed mine as well, though I went through the process of cleaning out the xcode organizer and reinstalling my provisioning profile as well. That may not have been necessary, but it seemed like a good idea at the time.

[toddkrabach]

Yes, you can leave the provisioning profiles associated to both certs in organizer (they will show with a yellow dot because there is no matching cert, but it won't cause a problem until you go to use it). The only thing that needs to be swapped out to switch between the dev accounts is the cert.

[saul102]

It's strange. I have the same issue. At first I thought I had resolved it by having my dev cert's on separate keychains and just making the appropriate keychain the default when I was building for a device or the app store. This worked fine for my personal dev license, but just today when I performed a dev build for my work profile I got the "ambiguous" error. I exported as advised in this thread and it worked fine. Odd though, that it didn't give me the same problem on my other certificate.

[toddkrabach]

I believe I read somewhere (I don't remember where, though), that you may only be able to sign with certs in the login keychain in the future. I had tried to go down that road as well, with no real luck. If someone else has more luck, I'd love to know about it, though.

Re: worked with other cert - It does seem to work with one of the certs; whichever gets precedence in Xcode's cert lookup process, which just takes the first match.