Xcode cannot find a distribution signing identity for the App Store
Missing Signing IdentitiesShort answer
A signing identity is a certificate plus its private key. If Xcode cannot find one, this Mac has the certificate without the key, or neither. List identities with the security tool. Then export the identity from the Mac that created it, or recreate the Apple Distribution certificate if your team is at its certificate limit.
Fix it fast
1Find out which cause you have
List the valid code-signing identities in your keychains. A distribution identity must appear here with its private key.
security find-identity -v -p codesigning2Match what you see, then jump to its fix
What does the error look like?
Missing Signing IdentitiesNo Matching Signing Identity or Provisioning Profiles FoundThe Private Key for Your Signing Identity Is MissingYour account already has a valid iOS distribution certificate
Cause 1 of 2
The private key is not on this Mac
1Check
A certificate is only usable for signing together with its private key. Apple's code signing troubleshooting note lists a missing private key as a cause of missing signing identities.
security find-identity -v -p codesigning2Fix
On the Mac that created the certificate, use Xcode to export your signing assets, and import them on this Mac. Apple's note points to the export and import steps in its App Distribution Guide for this.
# On the original Mac: use Xcode to export the signing assets (Apple App Distribution Guide: Exporting and Importing Certificates and Profiles)3Verify
The identity now appears in the list.
security find-identity -v -p codesigningConfirmed by developer.apple.com
Cause 2 of 2
The team already has the maximum number of distribution certificates
1Check
Apple explains that when this Mac lacks the certificate or its private key, Xcode tries to make a new pair and fails because the team is at its limit. Only one of each type of distribution certificate is allowed per team, and only the Account Holder or an Admin can create them.
security find-identity -v -p codesigning2Fix
Either bring the existing identity to this Mac as above, or, if it is lost, revoke and re-create the distribution certificate and update the related provisioning profiles. Apple notes that for App Store teams most missing-identity problems are solved by recreating certificates.
# Revoke and re-create the distribution certificate in your Apple Developer account (Account Holder or Admin), then update related provisioning profiles3Verify
Xcode creates or finds the identity and the archive signs.
security find-identity -v -p codesigningConfirmed by developer.apple.com
How do I stop it coming back?
- Keep a protected backup of the exported signing identity somewhere your team controls.
- Do not share certificates outside your organization.
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
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 fixMobile apps
App Store Connect rejects a screenshot because it has transparency
Images can't include alpha channels or transparencies.
App Store Connect does not accept screenshots that carry an alpha channel or transparent pixels.
2 causes, each with a fix