Xcode signing certificate or private key missing
Check the team, certificate identity, and private key on the Mac performing the build.
Check the team, certificate identity, and private key on the Mac performing the build.
Try these fixes in order
Identify signing mode
Review the failing target’s Signing & Capabilities and whether automatic or manual signing is selected.
Check account and keychain
Confirm Xcode is signed into the right team and the signing certificate includes its private key in the build machine keychain.
Check profile match
For manual signing, ensure the profile references the intended certificate and app ID.
Repair deliberately
Create or import an authorized signing identity; avoid revoking a shared distribution certificate without coordinating with the team.
Interpret what you see
Certificate appears in portal but not with a private key on Mac
What it suggests: A portal record cannot sign without its key material.
Next check: Import the authorized identity or create one through the team’s signing process.
Only one CI runner fails
What it suggests: Its keychain or signing credential setup differs.
Next check: Inspect runner keychain access and profile installation without exposing private keys.
The error names another team
What it suggests: The target or build configuration selects a different identity.
Next check: Compare team IDs, certificate names, and provisioning profiles across targets.
Why this happens
- The selected certificate is not installed with its private key.
- The profile, team, or build configuration refers to another signing identity.
Still not working?
A certificate visible in the developer portal is not sufficient if the Mac has no matching private key.
Official sources
These steps are based on the linked documentation and general diagnostics. BugMedic has not independently tested every product and system configuration. Review commands before running them.