Bitrise iOS step failed with error "xcode archive path not found" troubleshooting

TL;DR

Align the archive path the Bitrise step produces with the path later steps expect: check the Xcode Archive step output variable, the scheme and configuration names, and whether the archive step actually succeeded. Most failures are a renamed scheme, an export step reading a default path after a custom path was set, or the archive step failing silently above in the log. Read the step outputs rather than guessing file locations.

xcode archive path not found - Bitrise iOS step

Use this when

• A Bitrise deploy or export step fails saying the xcode archive path is not found.
• The workflow was cloned from another app or the scheme was renamed.
• The archive step shows green but downstream steps cannot find the .xcarchive.

Not for this skill when

• The archive step itself failed with a compile error. Fix the build error first; the missing path is a symptom.
• You run the same lane locally with fastlane. Local path issues differ from Bitrise step variables.

Steps

1. Open the failed build log and find the Xcode Archive step output section, which prints the exported archive path variable value. Verify: the exact path the step exported is copied from the log
2. Scroll above the failure to confirm the archive step itself succeeded and created a .xcarchive bundle. Verify: the archive step shows success and an archive creation line
3. Compare the path the failing deploy step reads, including any hardcoded path in the workflow, with the exported variable. Verify: the mismatch between expected and exported paths is identified
4. Replace hardcoded paths with the archive steps output variable in the deploy or export step inputs. Verify: the workflow references the variable instead of a literal path
5. Check the scheme and configuration fields match the project exactly, including capitalisation. Verify: scheme and configuration names match the shared scheme in the project
6. Rebuild the workflow. Verify: the deploy step finds the archive and produces the IPA
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

Bitrise steps communicate through exported environment variables, not fixed locations. When a workflow hardcodes a path from a tutorial or another app, any change in scheme, configuration or step version breaks the handoff. The archive usually exists; the consumer step is simply looking somewhere else, so the log of the producing step is the source of truth.

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

Bitrise xcode archive path not found deploy step

Step handoff phrasing; use the exported variable. 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.

BITRISEXCARCHIVEPATH missing workflow fix

Variable phrasing for the same alignment problem. 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: archive step skipped by conditions

A step condition can skip archiving on some triggers while deploy still runs. Check step run conditions per trigger. 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_dSN1RClBt-2lLmmcfZ5-7A