Fix: No Matching Provisioning Profiles Found in Xcode

Written by

in

Quick answer: Quit and restart Xcode first, as it often holds stale provisioning profile caches after an update. If the error persists, open Xcode Settings → Accounts to re-download your profiles (or delete cached .mobileprovision files from ~/Library first), then re-select the profile and signing certificate in Build Settings.

Why this happens

When you build or archive an iOS app using manual code signing, Xcode stores a reference to a specific provisioning profile UUID in your target’s Build Settings. You will see an error like Your build settings specify a provisioning profile with the UUID “...”, however, no such provisioning profile was found. or No matching provisioning profiles found whenever Xcode cannot locate that exact profile or pair it with a valid signing identity in your macOS Keychain.

This commonly happens right after upgrading Xcode, renewing a certificate, or regenerating a profile in the Apple Developer portal. Xcode caches provisioning profile metadata in memory and on disk, and an update can leave your project pointing to an outdated UUID or a profile that no longer matches your installed certificate.

It can also occur if you created a new .certSigningRequest and certificate without regenerating the provisioning profile, or if the private key for your signing certificate is missing from Keychain Access.

How to fix it

Work through these steps in order, testing a build after each one.

1. Restart Xcode completely

Before changing any settings, quit Xcode completely (⌘Q) and reopen your project. Xcode does not always reload provisioning profiles or Keychain changes while it is running—especially right after an Xcode update or after downloading a new profile.

Many developers find that a full restart is all it takes for Xcode to re-index existing profiles and pair them with the correct certificates.

2. Clear cached profiles and re-download them

If restarting alone does not work, force Xcode to refresh its local cache of provisioning profiles:

  1. Open Xcode Settings (⌘,, labeled Preferences in older Xcode versions) and go to the Accounts tab.
  2. Select your Apple ID and your development team.
  3. Click Download Manual Profiles (in older Xcode versions, click View Details… and then Download All).

If the stale profile reference still refuses to clear, delete the locally cached .mobileprovision files from disk so Xcode fetches clean copies:

# Check the standard macOS provisioning profile cache folders
rm -rf ~/Library/MobileDevice/Provisioning\ Profiles/*
rm -rf ~/Library/Developer/Xcode/UserData/Provisioning\ Profiles/*

After clearing the folder, quit Xcode (⌘Q), reopen it, return to Accounts, and download your profiles again. Restart Xcode one more time so the refreshed list is loaded into your project.

3. Re-select the profile and identity in Build Settings

Even after re-downloading your profiles, your target may still point to the old UUID. Reset the selection in your target configuration:

  1. Select your project in the Project Navigator and choose your app target.
  2. Open Signing & Capabilities (or General in older Xcode versions) and verify that the correct Team is selected.
  3. Switch to Build Settings and filter for Provisioning Profile and Code Signing Identity.
  4. Clear any hardcoded or missing profile UUID, then select your newly downloaded provisioning profile.
  5. Confirm that the Code Signing Identity matches the certificate type included in that profile (for example, Apple Development / iOS Developer for development profiles, or Apple Distribution / iOS Distribution for distribution profiles).

If you inspect your project.pbxproj file in source control, look for PROVISIONING_PROFILE or PROVISIONING_PROFILE_SPECIFIER lines—removing stale entries or letting Xcode rewrite them cleanly often resolves stubborn mismatches.

4. Switch to Automatic Signing (if manual profiles aren’t required)

If you do not have a strict requirement to manage provisioning profiles by hand, letting Xcode manage signing removes the need to track UUIDs:

  1. Open your target’s Signing & Capabilities tab.
  2. Enable Automatically manage signing (in older Xcode versions, set Provisioning Profile to Automatic in Build Settings).
  3. Confirm your Team is selected.

Xcode will generate and maintain XC:-prefixed provisioning profiles automatically and match them to your Keychain certificates. Manual signing is still useful for teams that share specific distribution profiles in CI/CD pipelines, but automatic signing is the most reliable choice for everyday local builds.

5. Verify your certificate has a private key in Keychain Access

A provisioning profile will not pair with a certificate unless the matching private key is also installed on your Mac:

  1. Open Keychain Access from Spotlight.
  2. Select the login keychain and click My Certificates.
  3. Find your Apple Development or Distribution certificate and check for a disclosure arrow next to it. Expanding it should reveal a private key.

If there is no private key—which happens if you downloaded a .cer file created on a different Mac—Xcode cannot sign with that certificate. Export the .p12 (certificate + private key) from the original Mac and import it into your login keychain, or create a new certificate from a .certSigningRequest generated on your current Mac and regenerate your provisioning profiles in the Apple Developer portal.

How to prevent it

  • Use Automatic Signing for local development: Let Xcode manage development profiles and reserve manual profiles for CI/CD or App Store distribution if your workflow requires it.
  • Regenerate profiles after renewing certificates: Whenever you create a new certificate from a .certSigningRequest, edit and re-download any manual provisioning profiles that use it.
  • Back up .p12 files securely: Export your distribution certificate with its private key as a .p12 file so you can move between Macs without breaking existing provisioning profiles.
  • Restart Xcode after major updates: Quit and relaunch Xcode after installing an update or modifying Keychain certificates so cached profile lists stay in sync.

FAQ

Why does Xcode say a provisioning profile UUID wasn’t found even after I downloaded it?

Xcode caches provisioning profile lists in memory and in ~/Library, and it does not always reload them immediately after a download or Xcode upgrade. Quitting Xcode (⌘Q), clearing the cached .mobileprovision files, and restarting forces Xcode to index the newly downloaded profile.

Should I delete XC:-prefixed provisioning profiles?

It is safe to delete XC:-prefixed profiles when clearing a corrupted local cache. Those profiles are managed and regenerated automatically by Xcode whenever Automatically manage signing is enabled.

When should I use Automatic Signing instead of manual provisioning profiles?

Use Automatic Signing for most solo projects and day-to-day simulator or device testing, as Xcode handles certificate pairing and profile renewals for you. Stick with manual provisioning profiles only when your team or CI/CD pipeline requires strict control over which exact profile and entitlements are used for distribution builds.

Sources & credits

Parts of this guide are adapted from content licensed under CC BY-SA 3.0; this article is shared under the same license.