Maaz Zindani

Loading the index…

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

Xcode says the profile does not include your signing certificate

ErrorProvisioning profile doesn't include signing certificate

Short 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.

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

Fix it fast

  1. 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 codesigning
  2. 2Match what you see, then jump to its fix

    1. 1find-identity shows no valid identity, or not the one the profile listsThe certificate or its key is not in this Mac's keychainFix
    2. 2The 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. 3The certificate was revoked or replaced recently, and automatic signing keeps the old profileA certificate was revoked and an old cached profile is still usedFix

What does the error look like?

  • Provisioning profile doesn't include signing certificate
  • No 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 codesigning

2Fix

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 type

3Verify

The identity appears in the list.

security find-identity -v -p codesigning

Confirmed by developer.apple.com

Did this fix it?

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 > Edit

2Fix

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 Xcode

3Verify

Build again with the downloaded profile.

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

Confirmed by developer.apple.com

Did this fix it?

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' build

Confirmed by developer.apple.com

Did this fix it?

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

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.