Did you also regenerate your provisioning profile? This sounds like the provisioning profile doesn't contain the certificate you've uploaded.
I had regenerated the profile, but it looks like perhaps the profile was attached to an old cert. I added both available certs I had (both show up with the same name in the Apple dev portal, unfortunately) and it worked.
Thanks for the pointer.
i am getting same error Error - Certificate doesn't match profile: The default keychain doesn't have an identity matching - You can fix this
hi, yeah i can confirm indeed the signing key is not linked to the mobile provision profile. you may have to re-export the mobile provision again once it is linked to your key.
Thank you very much van......
I'm getting the same error and even after reading this thread I don't understand why.
I can see no reason based on the steps I followed why they don't match and no idea how to fix it.
I tore down, started over and got it.
I hope this helps someone who is still having issues.
The solution for me was to create my p12 file by using KeyChain to export the Certificate created by Apple’s Developer Console. I have KeyChain version 7, and it will display Apple’s Certificate with a warning/error message, stating This certificate was signed by an unknown authority. This can be ignored.
Create your p12 file using the Certificate you created in Apple’s Developer Console. PhoneGap Build will accept the p12 file and Provisioning Profile created from the Developer Console Certificate.
I resolved this by revoking my old Apple Developers Certificate and by requesting a new one.
The problem was that I had created the certificate on another Computer. This does not work, because the private key which is getting exported to .p12 is only correct from original machine. That is why you need to request a new certificate from Apple and just follow these steps (http://docs.phonegap.com/phonegap-build/signing ) and everything should work.
How do you tear down? I keep seeing this is the only solution that works, all of the updating provisioning file and other linking is not clear to me and no one seems to clarify or state that it works.
Thanks for advising
1 person found this helpful
I think Howard meant that he started over from scratch, sort-of kind-of. Correct me if I'm wrong Howard.
Abtecas, if starting over from scratch doesn't work, or if it's a route you don't want to take, then try updating your MacOS to High Sierra(v10.13.1), and your KeyChain to v10.0.
If you can't update your OS or KeyChain, then give my solution a try. If that doesn't work, then thie KeyChain Solution Guide below will definitely point you in the right direction. The author keeps the guide up-to-date whenever he or someone else finds a show stopping bug/process with KeyChain, and he validates all of the findings. Here's the link:
I hope this helps.
What a bear of a problem!
I tried everything mentioned in this thread 10 times over - starting from scratch, you name it... without success.
Out of desperation, I took your advice and upgraded my Mac from Sierra to High Sierra. After that, I deleted any and all references to my old dev certs locally, then deleted my dev cert and provisioning profile from the Apple Developer site.
After that, I generated clean Dev Certs & provisioning profiles and it *finally* worked. What a PITA, but glad it worked out.
Thanks to all that have posted here!