Why am I getting an error "Failed to locate or generate matching signing assets" in Xcode 6?

Question

I installed the Xcode 6 GM seed, and I'm trying to create an IPA file for the first time. After archive success, when I click on the Export button, a window appears saying:

Failed to locate or generate matching signing assets

Xcode attempted to locate or generate matching signing assets and failed to do so because of the following issues.

• Your account already has a valid iOS Distribution certificate.

  If you have your signing identity on another Mac, you can import a developer profile. You can also revoke the current certificate and request one again.

Here's a screenshot of the error:

Can anybody tell me how to solve this?

Solution 1

In keychain access, -> Show Expired Certificates, then in your login keychain click on expired certificate and delete it. I also had the same expired certificate in my System keychain, so I deleted it from there too.

-> After deleting the expired cert from the login and System keychains,download certificate from below link and open with keychain.

Download https://developer.apple.com/certificationauthority/AppleWWDRCA.cer and add it to Keychain access > certificates (which expires on 2023)

this solved my problem

Solution 2

I edited distribution profile and downloaded it again, restarted xcode and it worked.

Solution 3

I have been searching answer for this problem past 6 hours. Nothing is satisfactory. As no one knows why this is happening. Following is way to generate .ipa via command line. If that works I will update here tomorrow.

xcodebuild -exportArchive -archivePath $projectname.xcarchive -exportPath $projectname -exportFormat ipa -exportProvisioningProfile "Provisioning Profile Name"

Note : The "Provisioning Profile Name" is the name specified in the name field of the certificate (viewable from developer.apple.com).

This will create .ipa.

credit goes to Orginal author here

This trick worked for me.

Solution 4

I got this error when having multiple development accounts/teams I was on. The solution for me was to make sure that all of the following were properly set up:

1. I had a distribution certificate with private key for the account the app belonged to (if someone else has made the certificate you have to key the private key from them and install it).
2. I had a specific (not wildcard) application ID (as in com.mycompany.myapp).
3. I had a provisioning profile that was created using the distribution certificate mentioned above along with the AppID mentioned above.

When all of that is in place, you can refresh your account in Xcode and you should not get that message anymore...

Solution 5

I got the same thing the first time, and then I realized that in the dev site there was a new provisioning profile that started with XC: I restarted xcode and xcode automatically found the XC: profile it created earlier and allowed me to sign the app. It looked as if the restart of xcode and refresh of signatures (after signing in while uploading/verifying the app on xcode) did the trick

View more solutions

Comments

[Igor Konoplyanko]

nothing works for me :( is the only option to download xcode 5 ?

[James]

Oddly enough, "Try Again" worked for me

[Alix]

Sadly no definitive solution or fix. Does anyone knows why this is happening ?

[matinict]

i also face same problem xcode 7.2 but not get solution

[warpedspeed]

Same here, just re-saved a new profile, installed it, and then restarted. Once I did this everything worked.

[Jeremy Hicks]

I just chose it in the list of provisioning profiles in the Member Center, selected edit, didn't change anything and saved.

[Alix]

I like your confidence but this was as fail as other answers.

[Alix]

Where would I import from when there is no earlier developer profile ?

[Guy Schalnat]

This was scary. I got an email saying my development certificate has been revoked. Admittedly, I don't really know what I am doing in xcode, but I can't recommend this to anyone, just in case it really does something bad.

[noir]

This is a dangerous answer as it's not necessarily addressing the issue, and for people who work in team environments, it's very likely that you don't want to revoke all Signing Identities. Do not follow this suggestions unless you absolutely understand what you're doing.

[SinisterMJ]

We had to burn the village to save the people.

[Magnus O.]

The download in this solution is what solved it for me. All my certificates where reported as invalid user before I downloaded this.

[Joshua]

Thanks for this post! It fixed the issue in my case.

[scosman]

Thanks! For anyone else: you don't need to delete all expired development certificates, just the Apple "Worldwide Developer Relations" Cert

[Ulysses]

I revoke and create a new distribution profile, download, add to xcode and work like a charm :)

[ALTVisual]

Worked for me. Has everyone who experienced this problem had their developer license expire before renewing? That's my case, was just curious about others.

[Yevhen Dubinin]

Same here. The thing is, When you choose the team, Xcode tries to figure out the signing "setup" by requesting the Developer Portal. And for some unknown reason it fails to do so. The last resort in this case would be to use local signing assets. Of course, if you are 100% sure, you have the correct "setup" locally already.

[Rozgonyi]

This helped because my problem was my Keychain Access had both the old expired certificate versions and the new versions of the same certificate. Once I deleted the expired ones, it found the newer ones fine.

[Saurabh Prajapati]

restarted the Xcode and it works. even In Xcode 10!