Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Xcode finds no provisioning profile for your bundle ID

ErrorXcode couldn't find any provisioning profiles matching

Short answer

Xcode has no development profile that fits your bundle ID, team and device. Check four things in order: an Apple Account is signed in and a team is chosen, Automatically manage signing is on and the device is registered, a manual profile is actually installed, and the bundle ID matches the App ID in the profile.

  • Applies to Xcode 26, iOS 26, macOS 26
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Print the signing settings Xcode really uses for the target, so you see the team, bundle ID and style before changing anything.

    xcodebuild -scheme MyApp -showBuildSettings | grep -E "PRODUCT_BUNDLE_IDENTIFIER|DEVELOPMENT_TEAM|CODE_SIGN_STYLE|PROVISIONING_PROFILE"
  2. 2Match what you see, then jump to its fix

    1. 1DEVELOPMENT_TEAM is empty in the first stepNo Apple Account is signed in, or no team is chosen for the targetFix
    2. 2CODE_SIGN_STYLE = Manual, or a Register button shows under SigningAutomatic signing is off, or the device is not registered in the profileFix
    3. 3CODE_SIGN_STYLE = Manual and a profile name is set, but Xcode cannot use itYou sign manually and the profile is not installed on this Mac, or is staleFix
    4. 4The profile exists, but for a different identifier (a typo, or a suffix added for a flavour)The bundle identifier does not match the App ID of the profileFix

What does the error look like?

  • Xcode couldn't find any provisioning profiles matching

Cause 1 of 4

No Apple Account is signed in, or no team is chosen for the target

1Check

Open Xcode > Settings > Apple Accounts and check that your account is listed with its team.

xcodebuild -scheme MyApp -showBuildSettings | grep DEVELOPMENT_TEAM

2Fix

Sign in under Xcode > Settings > Apple Accounts. Then, on the target's Signing & Capabilities tab, choose the team (or click Set Up Signing) and enter a bundle identifier.

# Xcode > Settings > Apple Accounts > add account; target > Signing & Capabilities > Team

3Verify

The team name shows under Signing and the error disappears.

xcodebuild -scheme MyApp -showBuildSettings | grep DEVELOPMENT_TEAM

Confirmed by developer.apple.com

Did this fix it?

Cause 2 of 4

Automatic signing is off, or the device is not registered in the profile

1Check

In Signing & Capabilities see whether Automatically manage signing is ticked. Apple states that with it on, Xcode registers the device and creates the development profile for you.

xcodebuild -scheme MyApp -showBuildSettings | grep CODE_SIGN_STYLE

2Fix

Tick Automatically manage signing, assign the team and bundle ID, choose the physical device as run destination, and click Register if that button appears.

# Signing & Capabilities: tick 'Automatically manage signing', then click Register

3Verify

Build for the device; Xcode creates the profile and the red error clears.

xcodebuild -scheme MyApp -destination 'generic/platform=iOS' build

Confirmed by developer.apple.com

Did this fix it?

Cause 3 of 4

You sign manually and the profile is not installed on this Mac, or is stale

1Check

Edit the profile in your developer account if it lacks a certificate or device, then download it again in Xcode. Apple notes automatic signing only requests a new profile when it cannot find a local one that satisfies the requirements.

ls ~/Library/MobileDevice/Provisioning\ Profiles/

2Fix

Regenerate or edit the profile under Certificates, Identifiers & Profiles, save it, and download it in Xcode. To force a new request, back up and remove the cached profiles in that folder and build again.

mkdir -p ~/profiles-backup
cp -R ~/Library/MobileDevice/Provisioning\ Profiles/. ~/profiles-backup/

3Verify

Build again; Xcode requests or finds a matching profile.

xcodebuild -scheme MyApp -destination 'generic/platform=iOS' build

Confirmed by developer.apple.com

Did this fix it?

Cause 4 of 4

The bundle identifier does not match the App ID of the profile

1Check

Apple's signing note says Xcode compares the project's bundle ID with the App IDs of the installed profiles, and an explicit App ID needs the same bundle ID.

xcodebuild -scheme MyApp -showBuildSettings | grep PRODUCT_BUNDLE_IDENTIFIER

2Fix

Make the bundle identifier in the target equal to the App ID of the profile, or create a profile for the identifier you use.

# target > Signing & Capabilities > Bundle Identifier = the profile's explicit App ID

3Verify

The signing section shows the profile name and no error.

xcodebuild -scheme MyApp -showBuildSettings | grep PRODUCT_BUNDLE_IDENTIFIER

Confirmed by developer.apple.com

Did this fix it?

How do I stop it coming back?

  • Keep Automatically manage signing on for development builds and use manual profiles only where a pipeline needs them.
  • Set the team and bundle ID per build flavour in the project settings, not by hand each time.
  • Download profiles again after you add a device or a capability to the App ID.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Related fixes

Mobile apps

App record creation fails because you lack permission

You cannot add a new app in App Store Connect as a Developer or limited user

Only the Account Holder, an Admin or an App Manager can create an app record, and Apple blocks it until the Account Holder has signed the latest agreement.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.