Xcode says the profile does not include your signing certificate
Provisioning profile doesn't include signing certificateShort answer
The profile Xcode picked was made for other certificates than the one you sign with. Either the certificate is not in this Mac's keychain, or it was never added to the profile, or Xcode is reusing an old cached profile. Add the certificate to the profile and download it again.
Fix it fast
1Find out which cause you have
List the code signing identities in your keychain, then compare them with the certificates named in the profile in your developer account.
security find-identity -v -p codesigning2Match what you see, then jump to its fix
- 1
find-identity shows no valid identity, or not the one the profile listsThe certificate or its key is not in this Mac's keychainFix - 2
The identity is valid in the keychain, but the profile in your account does not contain that certificateThe profile was created before the certificate and does not list itFix - 3
The certificate was revoked or replaced recently, and automatic signing keeps the old profileA certificate was revoked and an old cached profile is still usedFix
- 1
What does the error look like?
Provisioning profile doesn't include signing certificateNo unexpired provisioning profiles found that contain any of the keychain's signing certificates
Cause 1 of 3
The certificate or its key is not in this Mac's keychain
1Check
Apple's troubleshooting note says that when the profile is in Xcode's library but no matching certificate is in the keychain, the certificate must come from the Mac that created it. In Keychain Access a certificate with its key has a disclosure triangle.
security find-identity -v -p codesigning2Fix
Import the identity exported from the Mac that created it (double-click the .p12), or create a new signing certificate in Xcode under Settings > Accounts > Manage Certificates (+).
# Xcode > Settings > Accounts > your team > Manage Certificates > + > choose the type3Verify
The identity appears in the list.
security find-identity -v -p codesigningConfirmed by developer.apple.com
Cause 2 of 3
The profile was created before the certificate and does not list it
1Check
In Certificates, Identifiers & Profiles open Profiles, select the profile and compare its certificates with yours. Apple says you can edit a profile to add certificates, and must regenerate it if it is invalid or expired.
# developer account > Profiles > select the profile > Edit2Fix
Edit the profile, tick your certificate, save it, then download the profile in Xcode. If the profile is invalid or expired, choose Edit and click Generate.
# Profiles > Edit > add certificate > Save > download in Xcode3Verify
Build again with the downloaded profile.
xcodebuild -scheme MyApp -destination 'generic/platform=iOS' buildConfirmed by developer.apple.com
Cause 3 of 3
A certificate was revoked and an old cached profile is still used
1Check
Apple says Xcode only asks for a new profile when it cannot find a local one that meets the requirements, so a cached profile can be reused.
ls ~/Library/MobileDevice/Provisioning\ Profiles/2Fix
Back up the cached profiles, remove them from that folder, and build again so Xcode requests a fresh one.
mkdir -p ~/profiles-backup
mv ~/Library/MobileDevice/Provisioning\ Profiles/* ~/profiles-backup/3Verify
Build again; Xcode creates a profile that contains the current certificate.
xcodebuild -scheme MyApp -destination 'generic/platform=iOS' buildConfirmed by developer.apple.com
How do I stop it coming back?
- Export your signing identity as a .p12 and store it safely when you create it.
- Edit the profile and add the certificate whenever you create a new one.
- Prefer automatic signing, so Xcode keeps the profile and certificate in step.
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 finds no provisioning profile for your bundle ID
Xcode couldn't find any provisioning profiles matching
Xcode has no development profile that fits your bundle ID, team and device.
4 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