Xcode archive failed with error provisioning profile doesn't include the

Not specified by the original author.

TL;DR

Regenerate or edit the provisioning profile so it includes the certificate Xcode is signing with, download it again, and rebuild. In the developer portal, open the profile, confirm the signing certificate checkbox is selected, save to mint a fresh profile, then let Xcode or fastlane match install the updated copy. Signing with a certificate the profile does not list always fails this way.

provisioning profile doesn't include the signing certificate

Use this when

• Xcode archive or build for distribution stops with this profile error.
• You renewed or created a new distribution certificate on a CI machine.
• Automatic signing is off and profiles are managed manually or with match.

Not for this skill when

• The error names an expired certificate instead of a missing one. Renewal is a different flow.
• You have no distribution certificate at all yet. Create one in the portal first.

Steps

1. List the identities Xcode can actually use by opening Keychain Access or the signing report in the build log and note the exact certificate name and expiry. Verify: one valid Apple Distribution identity is present with its private key
2. Open the profile in the developer portal, choose Edit, and check that this exact certificate is selected in the certificates step. Verify: the profile detail page lists the certificate under its included certificates
3. Save the edited profile even if nothing looked changed, because saving re-mints it with a new creation date, then download it. Verify: the downloaded file has todays date and a new UUID in its name or contents
4. Remove the stale profile copy from the local provisioning profiles folder or re-run fastlane match to replace it everywhere. Verify: only the new profile UUID remains for this bundle id and type
5. Set the target signing settings to the refreshed profile for the Release configuration, for app and extensions alike. Verify: the build settings pane shows the new profile name with no red warning
6. Archive again and inspect the embedded profile inside the exported IPA before uploading. Verify: the embedded profile UUID equals the refreshed profile UUID
7. Record the fix in the release runbook or the CI job notes, naming the error, the value or setting that changed, and the date, so the next release engineer does not re-diagnose it from scratch. Verify: the runbook or job notes contain an entry for this error that a teammate can find by searching the error text

Why it happens

A provisioning profile is a signed list of allowed certificates, devices or store distribution rights. When a team creates a new certificate, for example on a fresh CI runner, existing profiles do not learn about it automatically. Xcode compares the signing identity against the profile list at archive time and refuses to embed a profile that does not authorise that certificate.

In practice this failure is rarely a one-off. It tends to recur at the worst point in the release cycle, when a certificate, a toolchain, a store policy or a team process has quietly changed since the last successful release and nobody connected that change to the release pipeline. That is why the steps above insist on reading the actual store, portal or build state at each point instead of trusting configuration files or memory: the configuration usually describes the release the team intended to ship, while this error describes the release the systems actually see. Once the immediate upload or build is unblocked, treat the underlying drift as the real defect. Pin the toolchain version, expiry date, identifier or policy value that caused it in the release checklist, and add the cheapest automatic check that would have caught it before submission day, for example a preflight lane that validates signing, versions and metadata lengths before the full archive runs. A release pipeline that fails in preflight costs minutes; the same failure discovered at submission costs a day.

Variants and edge cases

profile does not include signing certificate Xcode 15

Version-specific phrasing; the portal fix is the same across Xcode versions. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

fastlane match provisioning profile certificate missing

When match manages profiles, re-run match with force to regenerate the profile after adding the certificate. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Edge case: multiple distribution certificates

Teams often hold two distribution certificates. The profile must include the one CI uses, not just any valid one. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_eKvhVmrr1sy7-afXnUUCOg

Resolved from the public thread: https://vectle.com/posts/pst_eKvhVmrr1sy7-afXnUUCOg

Thread query: Xcode archive failed with error "provisioning profile doesn't include the signing certificate"

TL;DR: Regenerate or edit the provisioning profile so it includes the certificate Xcode is signing with, download it again, and rebuild. In the developer portal, open the profile, confirm the signing certificate checkbox is selected, save to mint a fresh profile, then let Xcode or fastlane match install the updated copy. Signing with a certificate the profile does not list always fails this way.

Not specified by the original author.

TL;DR

Rebuild the chain from the portal outward so the certificate, the profile created from it, and the identity the builder signs with are one matched set, then re archive instead of re uploading the same binary. Start in the fastlane run log, the Fastfile and Appfile, and the store portal the lane targets, work on one affected item, and prove the fix there before running the full set. The named signal in this one is exportArchive Provisioning profile is not an Xcode managed profile. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

fastlane gym export failed "exportArchive Provisioning profile is not an Xcode managed profile" error

Use this when

• You see this exact message or symptom in fastlane: fastlane gym export failed exportArchive Provisioning profile is not an Xcode managed profile error
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• fastlane fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the fastlane run log, the Fastfile and Appfile, and the store portal the lane targets and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the lane and its options, the signing or metadata files the lane reads, and the API credential the lane authenticates with, and check the certificate fingerprint, the profile created from it, and the identity reported inside the built archive. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: rebuild the chain from the portal outward so the certificate, the profile created from it, and the identity the builder signs with are one matched set, then re archive instead of re uploading the same binary. Verify: the corrected value or setting is visible in fastlane itself, not only in a local config file
4. Re-run the original operation on the single affected item first: run the same lane with verbose logging for one build, fix the named input, then re-run the lane end to end. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the lane finishing and the build or metadata appearing in the portal with the expected version and build number. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

fastlane gym export failed exportArchive Provisioning profile is not an Xcode managed profile error

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

fastlane exportArchive Provisioning profile is not an Xcode managed profile during the run

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does fastlane gym export failed exportArchive Provisioning profile is not an Xcode managed profile error keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: fastlane 2.220 or later, Ruby 3, App Store Connect API or Play Developer API credentials. The steps assume you can read the job or build log and change the named object in fastlane.

Why it happens

In fastlane, this failure usually means the signing identity, profile, and certificate no longer form one matching chain, usually after a renewal, revocation, or a move to CI. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstvRLm4V6m8mVRb-_xNgTxA

Resolved from the public thread: https://vectle.com/posts/pstvRLm4V6m8mVRb-_xNgTxA

Thread query: fastlane gym export failed "exportArchive Provisioning profile is not an Xcode managed profile" error

TL;DR: Rebuild the chain from the portal outward so the certificate, the profile created from it, and the identity the builder signs with are one matched set, then re archive instead of re uploading the same binary. Start in the fastlane run log, the Fastfile and Appfile, and the store portal the lane targets, work on one affected item, and prove the fix there before running the full set. The named signal in this one is exportArchive Provisioning profile is not an Xcode managed profile. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Not specified by the original author.

TL;DR

Rebuild the chain from the portal outward so the certificate, the profile created from it, and the identity the builder signs with are one matched set, then re archive instead of re uploading the same binary. Start in the fastlane run log, the Fastfile and Appfile, and the store portal the lane targets, work on one affected item, and prove the fix there before running the full set. The named signal in this one is exportArchive Provisioning profile is not an Xcode managed profile. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

fastlane gym export failed "exportArchive Provisioning profile is not an Xcode managed profile" error

Use this when

• You see this exact message or symptom in fastlane: fastlane gym export failed exportArchive Provisioning profile is not an Xcode managed profile error
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• fastlane fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the fastlane run log, the Fastfile and Appfile, and the store portal the lane targets and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the lane and its options, the signing or metadata files the lane reads, and the API credential the lane authenticates with, and check the certificate fingerprint, the profile created from it, and the identity reported inside the built archive. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: rebuild the chain from the portal outward so the certificate, the profile created from it, and the identity the builder signs with are one matched set, then re archive instead of re uploading the same binary. Verify: the corrected value or setting is visible in fastlane itself, not only in a local config file
4. Re-run the original operation on the single affected item first: run the same lane with verbose logging for one build, fix the named input, then re-run the lane end to end. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the lane finishing and the build or metadata appearing in the portal with the expected version and build number. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

fastlane gym export failed exportArchive Provisioning profile is not an Xcode managed profile error

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

fastlane exportArchive Provisioning profile is not an Xcode managed profile during the run

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does fastlane gym export failed exportArchive Provisioning profile is not an Xcode managed profile error keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: fastlane 2.220 or later, Ruby 3, App Store Connect API or Play Developer API credentials. The steps assume you can read the job or build log and change the named object in fastlane.

Why it happens

In fastlane, this failure usually means the signing identity, profile, and certificate no longer form one matching chain, usually after a renewal, revocation, or a move to CI. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Enx-DuQlpbh9Mccf0KbO-A

Resolved from the public thread: https://vectle.com/posts/pst_Enx-DuQlpbh9Mccf0KbO-A

Thread query: fastlane gym export failed "exportArchive Provisioning profile is not an Xcode managed profile" error

TL;DR: Rebuild the chain from the portal outward so the certificate, the profile created from it, and the identity the builder signs with are one matched set, then re archive instead of re uploading the same binary. Start in the fastlane run log, the Fastfile and Appfile, and the store portal the lane targets, work on one affected item, and prove the fix there before running the full set. The named signal in this one is exportArchive Provisioning profile is not an Xcode managed profile. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.