Can't build after renewing certificate

I am getting the XCode error:

This provisioning profile does not have a valid signature (or it has a valid, but untrusted signature)

I have been working on this project with no issues until my certificate expired. After renewing it the error started to pop up.

I have reconfigured all of my provision files and downloaded them, put the new certificate in my Keychain. I notice that in Organizer all of the old provisions are still listed. Can this cause problems, or does Xcode know to search for a valid one?

Obviously I’m not an Xcode expert (not even close). I have searched the forum and found a few topics but none of them helped.

I thought perhaps that I could delete the certificates and all provision files and start over. Not sure what to do.

Here are details from the build error:

This was happening in 1.7 so I finally started using Unity 3 and it happens there as well.

Apparently xcode doesn’t know which cert to choose so I guess you should delete the old one using the keychain utility.

Hi thanks for the reply. There is no old certificate, I just renewed the one I already had. I’m wondering though if i should just delete the certificate from the Dev Portal and start over. I can’t imagine this to be necessary though.

I’m waiting for more advice though before doing this.

:slight_smile:

How did you install the updated certificate?

Try Xcode → Empty Caches and Clean your project targets and see if that helps…I had a similar problem about a year ago and those actions appeared to resolve it.

[EDIT] after reading that error a little closer - do you have the cert in question listed in both your System and Login keychains? All of mine are installed in the Login keychain. It may be as simple as removing one or the other.

I double clicked to get it started, selected “login”. I think those were the only steps. I just now tried deleting it and reinstalling it, but it doesn’t ask me to go through the installation steps this time, it just appears back in Keychain Access as soon as I double click it.

@BoredKoi
I don’t have it installed as System.

Is this something that Dev Tech Support could help me with? I haven’t used any of my “incidents” since I signed up as a dev over a year ago.

Update:

I tried making a new App ID, then made new provision files using the new ID (racing3). I still get the same error!

I swear, this is maddening. i will gladly pay someone to help me if I must. I have lost 3 days worth of testing due to this and Apple is no help.

I found that in the System keychain there might be the old certificate BUT IT CAN BE INVISIBLE IF THEY ARE EXPIRED!!

:slight_smile: just go to “View → Show Expired Certificates”, then just see if the System keychain has the same certificate!

http://ericholsinger.com/programming/xcode-codesign-failed-with-exit-code-1-expired-certificates-causing-ambiguous-matches/