Xcode finds no provisioning profile for your bundle ID
Xcode couldn't find any provisioning profiles matchingShort 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.
Fix it fast
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"2Match what you see, then jump to its fix
- 1
DEVELOPMENT_TEAM is empty in the first stepNo Apple Account is signed in, or no team is chosen for the targetFix - 2
CODE_SIGN_STYLE = Manual, or a Register button shows under SigningAutomatic signing is off, or the device is not registered in the profileFix - 3
CODE_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
The 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
- 1
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_TEAM2Fix
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 > Team3Verify
The team name shows under Signing and the error disappears.
xcodebuild -scheme MyApp -showBuildSettings | grep DEVELOPMENT_TEAMConfirmed by developer.apple.com
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_STYLE2Fix
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 Register3Verify
Build for the device; Xcode creates the profile and the red error clears.
xcodebuild -scheme MyApp -destination 'generic/platform=iOS' buildConfirmed by developer.apple.com
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' buildConfirmed by developer.apple.com
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_IDENTIFIER2Fix
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 ID3Verify
The signing section shows the profile name and no error.
xcodebuild -scheme MyApp -showBuildSettings | grep PRODUCT_BUNDLE_IDENTIFIERConfirmed by developer.apple.com
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
Xcode says the profile does not include your signing certificate
No unexpired provisioning profiles found that contain any of the keychain's signing certificates
The profile Xcode picked was made for other certificates than the one you sign with.
3 causes, each with a fixMobile apps
Cannot change the App Privacy answers in App Store Connect
Publish Your App Privacy Responses?
Only the Account Holder, Admin and App Manager roles can answer the App Privacy questions.
2 causes, each with a fixMobile 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 fixMobile apps
You cannot find the button to pull your app back from review
No 'remove this version from review' message appears on the version page
There is no button called Reject Binary.
3 causes, each with a fixMobile apps
Your Apple Account cannot sign in to App Store Connect
Sign-in to App Store Connect is refused for an account that should have access
App Store Connect does not open to every Apple Account.
3 causes, each with a fixMobile apps
Apple rejected the app under Guideline 4.3, Design: Spam
Guideline 4.3(b) - Design - Spam
Guideline 4.3 is Apple's duplicate rule.
5 causes, each with a fix