Build settings defines a provisioning profile using UUID

Question

It seems I can not archive the application on a new computer. I created new profiles for distribution and development. I created a new certificate signing request. I can create an application on my iPhone, but I cannot archive it. I keep getting the error:

No matching training profiles found. The build settings indicate profiling using the UUID "BD657D9A -...", however such a provisioning profile. Xcode can fix this problem Downloading a new provisioning profile from the Member Center.

I tried to click “Fix Issue” and still remains an error. I deleted my certificates from the keychain and uploaded it again through the development portal, and this did not work. I tried to clear, rebuild, close Xcode, and all this does not work either. I tried to make various combinations of Code Signing-> Automatic, and also select the debug preparation profile as my development profile that I just created in the dev portal, and manually selecting the distribution profile that I just created in the dev portal, Both seem to be , does not work. Any other troubleshooting tips? Thank.

Answer 1

I am using Xcode 7.2 and have seen this problem. Restarting Xcode solved this for me. Not sure if he will always solve the problem, but you can try this first.

Answer 2

I know that it is too late to answer here, but this question rises up after searching for this problem. I managed to solve this problem by selecting a project, and in the Build settings changed the UUID parameters to what I wanted.

Answer 3

If you are using Xcode 7.2, you will see this message if you download individual profiles either from the Developer Center or from Xcode> Preferences> Account. Choose Team Name and View Details> Profile Profiles. I downloaded individual profiles (I have several dozen, so it’s hard to find a specific one) and ran into this error. Even if you selected Download All after downloading individual profiles, this error still appears.

You will need to find the Provisioning Profiles and delete them, then select Download All. The easiest way is to right-click on the profile in the account data that is already loaded, and select "Show In Finder" and delete all of them. Then just select “Download All” and hopefully your profiles will match your code signature.

See: Xcode 7.2 no matching training profiles found

Answer 4

I had this problem with Xcode 7.2 and the example that I downloaded from the tutorial website and tried to run it on my iPhone.

For me, this simple solution worked:

1) in the "Build Settings" section → "Code Signing": you will find the "hard-coded" UUID of the original creator → change this to "automatic" for debugging and release:

2) in the section "General" → "Identification" → Command: select a provisioning profile. You can also update the package ID if necessary.

3) "clean" is always a good idea after such changes, then builds

this solved the problem for me!

Answer 5

This is a known Xcode 7.1 issue. In my case, re-creating the profile was the only successful workaround

• Delete previous distribution profile in Member Center
• Restore distribution profile
• Archive with recreated profile

Answer 6

Removing DerivedData for the project worked for me:

 rm -rf ~/Library/Developer/Xcode/DerivedData/AppName 

Answer 7

Try using the iPhone Configuration Utility and the Xcode organizer to ensure that all certificates / regulations are configured correctly (they should be marked green). Check if your device is included in the certificate / software for Apple Developer.

Such checking and killing / opening Xcode (kill it completely when using Activity Monitor) worked for me

Answer 8

I upgraded Xcode7.1 to 7.1.1. Then I solved this problem.

Answer 9

I was getting the same error when trying to archive, trying to restart Xcode, clear, rebuild, nothing worked for a while. Then, with the target selected as my project, under the common identifier → Identity → Bundle, I simply deleted and then re-dialed the same (I know this is stupid!) The name of the package identifier, and then tried to archive again, this time worked. Such a crazy mistake.

Answer 10

There was the same problem ... Make sure the BUNDLE IDENTIFIER in the GENERAL Xcode view for your project matches what it reads the profile on your Dev web portal, and then that profile is set to Xcode verbatim. Select this profile in the BUILD setting, and you can be solved by now (the application is installed on devices without problems), but we also noticed that we can return to viewing GENERAL and the FIX button actually worked: the profile was “not found” fixed (once The "fixed" lock button disappears)

Answer 11

Many people have successfully copied profiles manually from their "Provisioning Profiles" folder to "~ / Library / MobileDevice" (including me). If this works for you, stop copying + pasting and linking to it!

$ sudo -i

# mkdir /Library/MobileDevice; ln -s /Users/myuser/Library/MobileDevice/Provisioning\ Profiles/ /Library/MobileDevice/ # mkdir /Library/MobileDevice; ln -s /Users/myuser/Library/MobileDevice/Provisioning\ Profiles/ /Library/MobileDevice/ - where myuser is your username.

Answer 12

Make sure your package ID matches the application ID in the developer portal. I had a com.company.MyApp package com.company.MyApp and app id com.company.MyApp

Answer 13

I solved this problem with the following steps:

• cd ~ / Library / MobileDevice / Provisioning \ Profiles /
• rm * .mobileprovision
• reset your position

Answer 14

Given all of the above. The only thing that worked for me was:

• Delete certificates and profiles from the developer portal
• Remove certificates and profiles from mac
• Recover certificates and profiles in the developer portal, download and install on Mac
• Remove package id on the General tab in xcode
• Re-add package id
• Assign new code signing profiles and signatures (dev and prod) when signing code x
• (clean again), build, deploy to device / simulator as a test
• Archive and download to the current version of itunes

In step 7, xcode requested access to the keychain (which it did not do in the other solutions mentioned above), after providing it, it worked.

The same goes for step 8.

Not sure what was happening (my certificates and profiles were only 3 months old), and I admit that it was a brute force method, but it worked.

Good luck.

Answer 15

I did everything that everyone offered, but none of them fixed my problem.

Using Xcode 7.3.1, what to fix:

Change the settings to run the application on the simulator. If he is configured to work on the device, and the udid device is not included in the training profile, he (erroneously) will yell at you.

Go to your project> Goal> Build Settings> Code Signing> Profile Profile and change it from "Automatic" to select the desired profile. At the moment, if you have not changed the application to run on the simulator, you may receive a warning to “Fix Issue”. Do not do this!

After you manually select your provisioning profile from the list, archive the application. Viola!

Answer 16

I opened project.pbxproj with a text editor and searched for the UUID and deleted a line like this PROVISIONING_PROFILE = "UUID";

Answer 17

Most of you will encounter this problem in the latest version of Xcode ie 7.1, so the solution I used for this is

• Assign code in Xcode 7.0
• Clear project
• Build a project
• Archive

All done.