CodeSign failed with a nonzero exit code during Xcode archive in Bitr

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 App Store Connect, the build processing page, and the version metadata page, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

CodeSign failed with a nonzero exit code during Xcode archive in Bitrise release workflow

Use this when

• You see this exact message or symptom in App Store Connect: CodeSign failed with a nonzero exit code during Xcode archive in Bitrise release workflow
• 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

• App Store Connect 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 App Store Connect, the build processing page, and the version metadata page 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 build binary details, the privacy manifest in the bundle, the version metadata and screenshots, and the rollout state, 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 App Store Connect itself, not only in a local config file
4. Re-run the original operation on the single affected item first: correct the named binary or metadata item, upload a new build number, and wait for processing to finish before resubmitting. 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 new build showing as processed and selectable, and the version status moving past the previous rejection point. 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

CodeSign failed with a nonzero exit code during Xcode archive in Bitrise release workflow

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

App Store Connect version of this failure

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 codeSign failed with a nonzero exit code during Xcode archive in Bitrise release workflow 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: App Store Connect, Transporter uploads, TestFlight processing, current App Store review guidelines. The steps assume you can read the job or build log and change the named object in App Store Connect.

Why it happens

In App Store Connect, 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_x0MEB35CsUP9cv7br5MwGA

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

Thread query: CodeSign failed with a nonzero exit code during Xcode archive in Bitrise release workflow

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 App Store Connect, the build processing page, and the version metadata page, work on one affected item, and prove the fix there before running the full set. 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 there are no local code signing identities found. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

fastlane sigh failed with error "there are no local code signing identities found" on CI

Use this when

• You see this exact message or symptom in fastlane: fastlane sigh failed with error there are no local code signing identities found on CI
• 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 sigh failed with error there are no local code signing identities found on CI

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 there are no local code signing identities found 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 sigh failed with error there are no local code signing identities found on CI 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_ReGlz87a3AppmuRyGACOIA

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

Thread query: fastlane sigh failed with error "there are no local code signing identities found" on CI

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 there are no local code signing identities found. 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/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.