Xcode 7.2 no matching provisioning profiles found

Question

Before upgrading Xcode to 7.2, I was using Xcode 7.1.1 to build and distribute apps. I have upgraded to Xcode 7.2 and none of my provisioning profiles (matched to that particular app's bundle ID) match my installed certificates that were working in Xcode 7.1.1.

I only get:

Your build settings specify a provisioning profile with the UUID “some_number”, however, no such provisioning profile was found.

I have tried regenerating a .certSigningRequest to generate a new Certificate and Profile and made sure the Team in the General tab of the target is correct. Whenever I select a Provision Profile, all of my Code Signing Identities appear in the Identities in Keychain, but none of them will pair correctly.

It seems setting the Provision Profile to Automatic and the Code Signing Identity to iOS Developer will resolve this error, but the advantage of managing my Provisioning Profiles is gone as I believe Xcode then manages these.

Any thoughts on why setting my Provisioning Profiles and Code Signing Identities to anything but Automatic and iOS Developer produces this error?

Medallist

Answer 1

I also had some problems after updating Xcode.

I fixed it by opening Xcode Preferences (⌘+,), going to Accounts → View Details. Then select all provisioning profiles and delete them with backspace (note: they can't be removed in Xcode 7.2). Restart Xcode, else the list doesn't seem to update properly.

Now click the Download all button, and you should have all provisioning profiles that you defined in the Member center back in Xcode. Don't worry about the Xcode-generated ones (Prefixed with XC:), Xcode will regenerate them if necessary. Restart Xcode again.

Now go to the Code Signing section in your Build Settings and select the correct profile and cert.

Why this happens at all? No idea... I gave up on understanding Apple's policies regarding app signing.

Spatter

Woah, that's weird! I was downloading individual profiles from that same view. I wonder why that wasn't working... And I was so excited that I could just download individual ones instead of cluttering the list with several dozen profiles... – Medallist

Just deleting the provisioning profiles and downloading again did not help. I have to quit Xcode and reopen again. – Sweetening

Great answer, could you add the tip below, to restart XCode? That seems to be the final step in getting this thing working – Feeder

It worked for me and its awesome answer.......Restarting the xcode was tricky. Thanks man – Salvidor

Wow - I wasted an hour trying to fix this before I found your answer which worked great. Why does Apple put us through this?? – Slipon

Thanks a lot. I also wanted to mention that Xcode automatically revoked one of my Distribution Certificates so keep that in mind. If you have many admins/members in your developer account this can lead to marking some of the provisioning profiles as invalid. Not quite sure that this is true, but I already received some complaints from the account agent – Surfperch

@the_Seppi it's of course possible that I've done something wrong, but I don't remember any manual revoking – Surfperch

Maybe they just expired? AFAIK, certs are valid for one year before a renewal is required. – Spatter

I hate Xcode so much when it comes to distributing to the App Store. When will they ever make this confounding process easier? – Brindle

Restarting Xcode after downloading all provisioning profiles was what I had to do. – Twiggy

I needed to restart my device as well – Fetter

I can't believe this worked...no idea why Apple's code signing phases are so damn buggy – Valorize

"I gave up on understanding Apple's policies regarding app signing" - You can have a +1 for that alone. My guess is that Apple's policies are mostly there to ensure that developers keep their $100/year Developer Program subscriptions up to date. – Polychrome

Xcode 7.3: You can no longer highlight (or delete?) Provisioning Profiles. Hitting backspace is just ignored. "Xcode. Each release makes you hate it just a little bit more. (tm)" – Showers

In Xcode 7.3, instead of hitting backspace, you can right-click on the profile and select "Move to Trash". – Greenwald

For me, Delete Profile -> Restart Xcode -> Install Profile -> Archiving .. works! – Jansson

WTF man this worked. Xcode sucks when it comes to app distribution. They could learn a thing or two from android to keep things simple. – Strauss

This answer is outdated as the options Accounts -> View Details suggested in the answer do not exist on the current Xcode. Stack really needs to learn to weed out old responses so they stop appearing as the top result on google. – Pizarro

Answer 2

Try restarting XCode first, before trying these other answers. I was about to follow the advice given in other answers, then noticed multiple people saying that restarting XCode was necessary after all the steps. All I did was restart XCode and it fixed the problem. Who knows if it'll fix the problem for you, but it's worth a shot before trying the other solutions. I'm on XCode 7.2.1.

Dairying

Very good advice - thanks! I had this issue with my AdHoc build while the Release worked fine. – Malcolm

yes, Download the PP, then select it, then restart XCode, it worked for me. – Streetlight

Yep - try the restart first. It fixed it for me. – Invention

This fixed it for me as well! Thanks. – Phia

an amazing advice! – Tortosa

~6 weeks later and I'm back to this answer. Restarting Xcode seems to work every time. I would up vote again if I could. – Phia

Answer 3

Keep quitting Xcode until the damn thing works.

Fatidic

Answer 4

I've also the same problem, in Xcode 7.2

It solved by followings steps:-

1) Open Xcode preference,

2) Select the appropriate team,

3) Click the "View Details..".

4) In section "Signing Identities": click on "Reset" for each of them.

5) In section "Provisioning Profiles". Click on "Download All".

6) Click on "Done."

7) Go in Xcode, build settings, select it. In General tab, the issues should get removed.

8) Restart the Xcode.

9) Do the Final build.

That's all.

Vaas

I followed all the steps.. but sill i am getting the same error, even after the restart – Riordan

restarting xcode was the big one for me... cant believe that apple doesnt even reccomend you to restart it – Stomato

I also searched the project folder for the UUID string and found it in "project.pbxproj". After blanking it out, build went fine. Change "PROVISIONING_PROFILE[sdk=iphoneos*]" = "82f0b3c1-a2d2-4202-9326-5eb37d8e41b8"; to "PROVISIONING_PROFILE[sdk=iphoneos*]" = ""; – Inkstand

Good finding @Inkstand – Vaas

I'm on Xcode 7.3 aswell. I followed this tips, and still have the same problem. Xcode. Each year, I hate it just a little bit more. – Showers

This is really horrible advice in team environments. Nobody should ever press the magic reset buttons in Xcode. – Jillene

@Inkstand that is the ONLY thing that worked for me. Thank you! – Dragnet

Answer 5

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

Waterscape

This is a separate issue as seen here: #32821689 – Medallist

Answer 6

Also after I did all of suggested steps (btw, for some reasons backspace not remove provision profile) error keeping occurring. Until I finally figured out to Restart Xcode. Probably, it should be first step when you're dealing with Xcode :)

Radcliff

I followed all the ideas.. but sill i am getting the same error, even after the restart – Riordan

@NikeshK, If you're sure that everything is correct and this is certainly Xcode bug, then you could try reinstall Xcode. Especially, if you didn't reinstall it for years and only roll updates over. – Radcliff

@NikeshK, also if your provision profiles was generated before last renewal update of Apple Developer program you also should recreate profiles. I did it like this: go to developer.apple.com, then to Provision Profiles sections, for all of profiles I clicked Edit, Save, Done - nothing changed inside, but expiration date will updated. After this step you need to redownload them through xcode – Radcliff

For me also, backspace/delete key did not work. Right click with mouse, and select 'Move To Trash'. – Furmenty

Answer 7

Using Xcode 7.3, I spent way too much time trying to figure this out -- none of the answers here or elsewhere did the trick -- and ultimately stumbled into a ridiculously easy solution.

1. In the Xcode preferences team settings, delete all provisioning profiles as mentioned in several other answers. I do this with right click, "Show in Finder," Command+A, delete -- it seems these details have changed over different Xcode versions.
2. Do not re-download any profiles. Instead, exit your preferences and rebuild your project (I built it for my connected iPhone). A little while into the build sequence there will be an alert informing you no provisioning profiles were found, and it will ask if you want this to be fixed automatically. Choose to fix it automatically.
3. After Xcode does some stuff, you will magically have a new provisioning profile providing what your app needs. I have since uploaded my app for TestFlight and it works great.

Hope this helps someone.

Hazelton

worked for me, but not with the same sequences of steps. My advice is to repeat these steps more that once adding some actions (build, quit and restart Xcode, etc) – Inherent

It's Jul 2017 but you solutions is the only one working for me ;) – Eliciaelicit

Answer 8

Check your Keychain - look in Login and System keychains for expired certificates or error messages.

I found certs with "this certificate has an invalid user" error messages, and an expired Apple Worldwide Developer Relations Certificate.

Delete them and install the new AWDRC certificate from https://developer.apple.com/certificationauthority/AppleWWDRCA.cer

Then follow the accepted answer to get Xcode to use the new certificates.

Delitescence

This is a separate issue as seen here: #32821689 – Medallist

I didn't get that error message, I got the exact one the OP had. – Delitescence

Answer 9

For me I tried following 2 steps which sadly did not work :

• deleting all provisional profile from Xcode Preferences Accounts → View Details , downloading freshly all provisional profiles.
• Restarting Xcode everytime.

---

Instead, I tried to solve keychain certificate related another issue given here This certificate has an invalid issuer Apple Push Services

This certificate has an invalid issuer

• In keychain access, go to View -> Show Expired Certificates.
• Look for expired certificates in Login and System keychains and an "Apple Worldwide Developer Relations Certification Authority".
• Delete all expired certificates.
• After deleting expired certificates, visit the following URL and download the new AppleWWDRCA certificate, https://developer.apple.com/certificationauthority/AppleWWDRCA.cer
• Double click on the newly downloaded certificate, and install it in your keychain. Can see certificate valid message.

Now go to xcode app. target → Build Setting → Provisioning Profile . Select value from 'automatic' to appropriate Provisioning profile . Bingo!!! profile mismatch issue is solved.

Ensheathe

This was actually a separate issue as seen here: #32821689 – Medallist

May be yes,however,at least in my case solving this fixed mismatch provisional profile issue . – Ensheathe

Which ultimately solved the xcode 7.2 workaround which had forced me to keep xcode 'Code signing' as 'automatic', to run app on devices. – Ensheathe

Answer 10

In my case, the problem was that the Archive was being built with a different TEAM-ID than the one who generated the Provisioning Profile (Me). Therefore I Got the error:

"No matching provisioning profile found: Your build settings specify a provisioning profile with the UUID, however, no such provisioning profile was found."

To Solve this:

• Clean and Re-Download your Provisioning profiles from Settings
• Re-Start Xcode

• in the GENERAL Tab of the Project properties, got to TEAM:

• Change the current team to the Same team but the one under the ACCOUNT you generated the provisioning profile with.

• Clean & Build

• Viola!

Hope this helps someone.

Mattins

Answer 11

I updated to Xcode v7.3.1 and it solved the issue.

Warden

Thanks! Fixed it for me too. I upgraded from 7.3.0->7.3.1. – Apologize

Update did not fix for me unfortunately – Sanburn

Answer 12

With Xcode 7.2.1, if you are certain that your provisioning profile is correct (it has the correct App ID and certificate, and the corresponding certificate exists in your Keychain Access) then set the Code Signing Identity and set the Provisioning Profile to Automatic.

Bernadinebernadotte

Answer 13

What I did was: created a new provisioning profile and used it. When setup the provisioning profile in the build setting tab, there were the wrong provisioning profile numbers (like "983ff..." as the error message mentioned, that's it!). Corrected to the new provisioning profile, then Xcode 7.2 refreshed itself, and build successfully.

Coterie

You could also set it to "Automatic" for all the entries under Provisioning Profile. That worked for me – Fye

Answer 14

Solutions described here work, but I want to add that you need to have correct target selected on the top left corner of Build Settings in Xcode. Lost some time figuring this out...

Lalitta

Answer 15

In Xcode 7.3 I got the same error, my certificate and provisional profile both were fine still I was getting the same error, I was unable to delete the provisional profile in Xcode preferences, so I tried by right-clicking on the provisional profile which shows the option to move to trash, but when I clicked nothing happened then I closed the preference window and open it again by Command, the provisional profile was gone and download option was visible, I clicked download and it starting working fine

Caucasia

Answer 16

You can easily fix the problem by changing bundle identifier on the Apple web page from com.my.app to com.my.app.iOS. I found this solution at https://forums.developer.apple.com/thread/15712.

Cirrus

Answer 17

When distribute to App Store, you choose Product -> Achieve and encounter "code sign error, no matching provisioning profiles found", if account and downloaded .mobileprovision file is ok. Try click the "Build and Run" button to run it on your phone.

And, a dialog box will popup with a button "Fix", just click "Fix" to do next... Last, your device will have an valid provisioning file. Just do "Product -> Achieve" again, everything is OK!

Stoner

Answer 18

You can also simply go to xcode preferences then accounts and then it may ask you to simply re sign in with your developer profile and then the issues should go away.

Hope this Helps!

Jacobsohn

Answer 19

For me changing the build configuration from release to Debug solved the issue.

You can find Build Configuration in Edit Scheme -> Run -> Info -> Build Configuration

Clean your project and re run.

Bencher

Answer 20

In addition to what other users posted, make sure the Team selected on the Target settings (General tab) is the correct one. Xcode will complain it cannot find the Provisioning Profile if the profile belongs to a different team than the one selected.

Greenwald

Answer 21

For me nothing above worked with XCode 7.3.1 because I had nothing in provisioning profiles (expired). I had to connect my iPhone to Mac and then click on Fix provisioning profile which created another profile expires in a week.

Aardwolf

Answer 22

For everyone who didn't solve it yet, my Issue was answered by this:

https://mcmap.net/q/152891/-xcode-8-1-quot-no-matching-provisioning-profiles-found-quot-after-updating-macos-and-xcode

Subatomic

Answer 23

After I have a few hours searching and trying I have two solutions 1- run the app using IOS real device. 2- turn off the automatically manage signing, go to https://developer.apple.com/account/resources/profiles/, and create a profile now on the Provisioning Profile import it and done.

Tripos

Answer 24

For me none of the solution worked, but If i disconnect the phone from laptop and then run the build, it succeeds and then I connect and run on the phone. I still couldn't figure out the final fix.

Peltry