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?
I got same issue. I was pretty sure about my provisioning and certificate etc are properly set. I created all these at apple dev portal while my Xcode 6.2 was opened. After downloading certificate and provisioning, I double clicked both and then was able to choose for signing from Xcode. That is NO Xcode restart needed up-to this point as new provisioning file is available to be chosen from Xcode. Then I archived the binary and it opened in Organizer for submission.
But here comes the actual issue that Organiser is not aware about my true assets. So, here we need to restart the Organiser (Xcode). I must say a bug at Apple's end to not make Organiser aware about the updated assets. As after restarting the Organiser, I submitted the app and it prompted to allow to sign certificate from Keychain.
I was also facing the same issue when using Xcode 6 GM and so I used Xcode 5.1 to create the ipa file.
In XCODE 6 when we create a provisioning profile it should be of type ADHOC.Set the profile in build settings and then archive.Everything will work fine I guess
In my case "Xcode 7.3" all i needed was to clean the project, restart Xcode, re-archive and it's all fine.
To fix this, I had to disable Automatic signing management in Target > General and import both dev and pro profiles after downloading them from my Apple dev account. Rebuilt app and it worked, nothing else did. I guess this issue can come from many different sources.
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:
When all of that is in place, you can refresh your account in Xcode and you should not get that message anymore...