It seems that there are a myriad of things that can go wrong and here's yet another (at least this ended up being my problem):
When creating my Certificate Request for a new iPhone Developer Certificate (after my old one expired), I entered the email address that Apple has on file for me in my developer profile. However, this email address isn't the same email address that I used to CREATE my iPhone Developer account.
Even if you've updated your profile information, you must still use the email address that you used when creating your account.
Yes, the "How-to" guide says, "Enter the email address you used when you created your account" but I (mistakenly) assumed that Apple would be smart enough to use your CURRENT email account. It seems to me that there should be a warning about that but... oh well.
What is more frustrating is that Apple went ahead and issued the certificate, and in the keychain utility, it listed the certificate as being valid. However, XCode was never able to use it. I'm not sure how that all works (nor do I care at this point) but it ended up causing DAYS of frustration.
In the end, I deleted all of my certificates and mobile provisioning profiles and started from scratch. I called Apple to make certain that I was entering the email address and name (sometimes I used my middle initial and sometimes I don't) that was used when the account was created and... VOILA.
I'm now off to drink profusely and forget all about Code-Signing problems until after the weekend.
Hope this helps some poor soul.
Quote:
Originally Posted by husoft
I had the same problem as joni
"A valid signing identity matching this profile could not be found in your keychain."
Solved it with just this step:
in Keychain Access right clicked "login" keychain and set it to default.
Restarted Xcode and all is good again. Have no idea what caused the problem.
|
