Xcode5 "No matching profile profiles found" (but good for xcode4)

Everything is fine on Xcode4.6. When I try to use Xcode5 dp6 to run the application on devices. I received the error "Missing appropriate profiling profiles." How can I solve this problem?

enter image description here

+51
xcode provisioning-profile
Aug 27 '13 at 21:41
source share
12 answers

Do not forget to change the profile in the "Profile profile" section: enter image description here

Ideally, you should see Automatic in Code Signing Identity after choosing the profile you need. If you do not see any option, which means that you do not have a private key for the current provisioning profile.

+93
09 Oct '13 at 6:08 on
source share

What really confused me was that there are two different sets of build settings: 1) for the project 2) for the purpose

In the sidebar (top left) there is a blue icon that represents your project. Click this: enter image description here

Then in the main panel on the right, in the upper line, to the left of the word "General", there is a small icon of your project. Click this, and now select a target from the popup menu:

the target selection

After you select Target, you can now change the build parameters for the target. They differ from the projects of the project itself ... strange! I'm not sure why there are build settings for the project as a whole, which are different from the target, since the Target settings are what is used during construction. So why do you even have settings for the project? Not sure.

But how do you change them. This solved the problem for me: go to Target (not the project!) In the Code Signing section> Preparation Profile> and change the settings to the appropriate profile. For a long time, I just changed them only in Project, because I did not know that I had to choose Target, and I had such a problem. This fixes it!

+51
Sep 23 '13 at 18:17
source share

Set up a migration profile profile. It confused me a bit until I found it.

  • Select a project file (to open the target)
  • Go to the "Build Settings" tab
  • Scroll down to “Signature Codes” and look there for a new section “Profiling”.

enter image description here

+7
Sep 23 '13 at 13:27
source share

OK - all of the above answers are correct to some extent, but did not solve this problem for me. I am using Xcode5.

There are many threads around this common error, but from what I read, it is an error in Xcode relating to versions 3.x that can randomly create conflicts with your Keychain.

I was able to solve this problem by following these steps:

  • Open Xcode -> Preferences -> Accounts: Delete Developer Account

  • Open Keychain: select Keys, delete all iOS keys; Select My Certificates, delete all iPhone certificates

  • Go to '/ Users // Library / MobileDevice / Provisioning Profiles', delete all the files (here Xcode stores mobile profiles)

  • Open Xcode -> Preferences -> Accounts: re-add your developer account

  • Go to the project objects, goals, General tab, and you will see the following enter image description here

  • Click "Feedback and request" (I tried this, it may take several minutes) or "Import a developer profile" (or downloading from the Apple developer portal and importing this method should be faster ..)

  • FINALLY: you can go to the build settings and set the "Preparation Profile" and "Signature Settings", as described by everyone here.

Doing this and only this resolved this error for me.

+6
Oct 24 '13 at 20:18
source share

Here is a simpler solution that worked for me:

In Xcode5, double-click your application icon. This will bring up the Info panel for the purpose. In the "Build Settings" section, check the "Code Signing" section for any old profiles and replace it with the appropriate one. update the value of "code signature identifier" and "provisioning profile"

+3
Sep 23 '13 at 0:19
source share

Sometimes, especially after creating a new certificate or starting to use a new code signing identifier, there seems to be no other way to fix this except by doing some cleaning up of the .pbxproj file. This is probably a bug that will be fixed, so if you read this long after this post, you might want to try a different solution.

The pixeldock blog has a great article: http://www.pixeldock.com/blog/code-sign-error-provisioning-profile-cant-be-found/

In short, basically quoting this article, you need to:

  • Make sure that you have extracted all your deleted iTunes Connect certificates in xcode5 from Settings, Accounts, (select your account), View Details, click the Renew button. (I usually answer no when xcode asks if I want to create certificate signing requests, this is not necessary when you only want to upload / renew your certificates).
  • Close Xcode
  • Right-click on your .xcodeproj bundle projects to display its contents.
  • Open the .pbxproj file in a text editor of your choice (first back up if you feel paranoid)
  • Find all lines in this file that include the word PROVISIONING_PROFILE and delete them.
  • Open xcode
  • Enter your goal and select the training profile that you want to use.
  • Create your own project

Good luck

+2
Dec 06 '13 at 7:00
source share

In xcode5 from "Settings", "Accounts" (select your account), "View details", click the "Update" button. then select “Profile Profile” in the build settings.

+1
Dec 09 '13 at 9:17
source share

In my case, the "Fix Issue" button starts the counter for 20 seconds and does not fix anything.

This works for me (iOS 7 iPhone 5, Xcode 5):

Xcode> Window> Organizer> Devices

Locate the connected device (with a green dot) in the left pane. Select "Profile Profiles" There is a warning line in the right pane. Delete this line.

Now go back to click the "Fix error" button, and everything is fine - the application starts on the device, as expected.

+1
Feb 08 '14 at 13:13
source share

I have 2 goals in my Free and Paid project. My mistake was that I looked at my free target, trying to build a paid target, a stupid mistake, but maybe one of it could also know about it.

+1
May 01 '14 at 17:59
source share

I get the same question that you can click here:

About the question in xcode5 "no matching training profiles found"

(No matching training profiles found for xcode5 的)

When I installed iOS7, I get a warning as follows: no matching provisioning profiles were found. the reason may be that your project is in a different group.

Do this: find the file with the name * .xcodeproj in your protection, show its contents.

You will see three files:

  • project.pbxproj
  • project.xcworkspace
  • xcuserdata li>

open the first one, do a uuid search and delete the line.

0
Mar 08 '14 at 3:32
source share

All the drop-down lists disappeared in the build settings after the patch was launched in Xcode 5. For several days we tried to find out what was wrong with my profile profiles and code signing. I found the Xcode 4 link missing the drop-down lists in the build settings and, of course, I had to turn on "Show Values" in the "Editor" menu again. Hope this helps someone else in this predicament.

In addition, I had to clear the received data, clear the solution, and exit and open Xcode again to correctly display the code signature identifiers. My distribution profiles are profiles that appear as signed by my developer certificate, which was incorrect.

0
Apr 05 '14 at 3:56
source share

I had the same error today, with Xcode 6.1

I found that no matter what I tried, I could not get Xcode to stop complaining about this Provisioning Profile with its GUID.

The solution was to look for this GUID in the pbxproj file, which is located in the Xcode folder. xcodeproj .

Just find the line containing your GUID:

 PROVISIONING_PROFILE = "A9234343-.....34" 

and change it to:

 PROVISIONING_PROFILE = "" 

One more thing to check: your Xcode PROJECT settings contain the Provisioning Profile and Code Signing settings, but there is a second set in the TARGETS tab.

So, if Xcode complains about the Provisioning Profile, which is not specified in the settings of your project, then go to the settings shown in the "TARGETS" section in your Xcode project.

(I would like someone to give me this advice, 4 painful hours ago ..)

0
Nov 26 '14 at 14:45
source share