fastlane gym export failed exportArchive Provisioning profile is not

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.

Not specified by the original author.

TL;DR

Install the provisioning profile that matches the bundle id, distribution type and current certificate, then point the target at it. Run fastlane match for the right type, or download the profile from the portal and confirm its app id and expiry. gym fails at export because the archive was signed for one profile and the export options demand another, so align the export method, profile mapping and installed profiles.

no matching provisioning profile found

Use this when

• fastlane gym or build_app fails at export with this message.
• Profiles were renewed in the portal but not synced to this machine.
• The export options plist names a profile that does not exist locally.

Not for this skill when

• Automatic signing in Xcode succeeds locally. The gap is specific to the gym export configuration.
• The bundle id changed recently. Profiles for the old id will never match; create new ones.

Steps

1. Read the gym log to capture the exact bundle id and profile name the export step requested. Verify: the requested bundle id and profile name are copied from the log, not guessed
2. List installed profiles and check whether one exists for that bundle id with the app-store type and a future expiry. Verify: a matching unexpired profile is either found or confirmed missing
3. Run fastlane match appstore, or the type gym requests, to fetch or regenerate the profile. Verify: match completes and reports the profile installed
4. Fix the export options so the provisioningProfiles mapping keys the bundle id to the installed profile name. Verify: the mapping in the Gymfile or export options matches the installed profile exactly
5. For app extensions, repeat the check per extension bundle id, since gym exports all targets together. Verify: every target bundle id has a matching profile listed
6. Re-run the gym lane. Verify: gym produces the IPA and prints its path with no profile error
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

gym archives fine with a development or generic signing setup, then the export step re-signs for distribution using the profiles named in the export options. If that named profile is absent, expired or built for a different bundle id or certificate, export aborts. The mismatch usually appears after profile renewal, because the new profile has a new name and UUID while build settings still reference the old one.

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

gym no matching provisioning profile found fastlane

The lane-level phrasing; sync match and fix the export mapping. 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.

no matching provisioning profile found Xcode export

Same root cause through Organizer export instead of fastlane. 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: renamed profiles

Portal-regenerated profiles change names. Any hardcoded profile name in CI must be updated or replaced with match-managed names. 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_ec2ipYQA9vJQ607MOorCbA

Resolved from the public thread: https://vectle.com/posts/pst_ec2ipYQA9vJQ607MOorCbA

Thread query: fastlane gym failed: "no matching provisioning profile found" error

TL;DR: Install the provisioning profile that matches the bundle id, distribution type and current certificate, then point the target at it. Run fastlane match for the right type, or download the profile from the portal and confirm its app id and expiry. gym fails at export because the archive was signed for one profile and the export options demand another, so align the export method, profile mapping and installed profiles.