iOS distribution certificate revoked suddenly: certificate is not trusted code

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 Expo EAS dashboard, the build log, and eas.json, work on one affected item, and prove the fix there before running the full set. The named signal in this one is failed to set up signing credentials for distribution certificate. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Expo EAS build failed "failed to set up signing credentials for distribution certificate" troubleshooting

Use this when

• You see this exact message or symptom in Expo EAS: Expo EAS build failed failed to set up signing credentials for distribution certificate
• 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

• Expo EAS 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 Expo EAS dashboard, the build log, and eas.json 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 EAS build profile, the credentials EAS holds for the app, and the App Store Connect app identifier in the submit profile, 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 Expo EAS itself, not only in a local config file
4. Re-run the original operation on the single affected item first: run one EAS build for the failing profile, fix the credential or identifier the log names, then submit that build. 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 build finishing in the EAS dashboard and the submit step reporting the correct store app. 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

Expo EAS build failed failed to set up signing credentials for distribution certificate

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

Expo EAS failed to set up signing credentials for distribution certificate 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 expo EAS build failed failed to set up signing credentials for distribution certificate 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: Expo SDK 51 or later, EAS Build and Submit, eas.json profiles. The steps assume you can read the job or build log and change the named object in Expo EAS.

Why it happens

In Expo EAS, 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_UoOCOid7ccWHexfuTc4iWQ

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

Thread query: Expo EAS build failed "failed to set up signing credentials for distribution certificate" troubleshooting

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 Expo EAS dashboard, the build log, and eas.json, work on one affected item, and prove the fix there before running the full set. The named signal in this one is failed to set up signing credentials for distribution certificate. 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 Expo EAS dashboard, the build log, and eas.json, work on one affected item, and prove the fix there before running the full set. The named signal in this one is provisioning profile does not include the currently selected device UDID. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

EAS build iOS failed "provisioning profile does not include the currently selected device UDID" error

Use this when

• You see this exact message or symptom in Expo EAS: EAS build iOS failed provisioning profile does not include the currently selected device UDID 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

• Expo EAS 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 Expo EAS dashboard, the build log, and eas.json 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 EAS build profile, the credentials EAS holds for the app, and the App Store Connect app identifier in the submit profile, 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 Expo EAS itself, not only in a local config file
4. Re-run the original operation on the single affected item first: run one EAS build for the failing profile, fix the credential or identifier the log names, then submit that build. 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 build finishing in the EAS dashboard and the submit step reporting the correct store app. 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

EAS build iOS failed provisioning profile does not include the currently selected device UDID 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.

Expo EAS provisioning profile does not include the currently selected device UDID 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 eAS build iOS failed provisioning profile does not include the currently selected device UDID 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: Expo SDK 51 or later, EAS Build and Submit, eas.json profiles. The steps assume you can read the job or build log and change the named object in Expo EAS.

Why it happens

In Expo EAS, 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_YKpoF5YpC8SzbzRr8oN5zQ

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

Thread query: EAS build iOS failed "provisioning profile does not include the currently selected device UDID" 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 Expo EAS dashboard, the build log, and eas.json, work on one affected item, and prove the fix there before running the full set. The named signal in this one is provisioning profile does not include the currently selected device UDID. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.