fastlane match failed with error "couldn't decrypt the repo" using a passphrase

TL;DR

Use the exact passphrase the match repository was encrypted with, supplied through the match passphrase environment setting in CI or entered interactively, and confirm it against the machine that last updated the certificates. If the passphrase is truly lost, the stored certificates cannot be recovered: revoke them in the portal, clear the match repo, and regenerate with a new passphrase stored in the team secret manager. There is no bypass for the encryption.

couldn't decrypt the repo - fastlane match

Use this when

• fastlane match fails immediately saying it could not decrypt the repo.
• CI cannot decrypt while a teammates machine can, or the reverse.
• The passphrase was rotated or the CI secret was overwritten.

Not for this skill when

• The git clone itself fails with an authentication error. That is repository access, not decryption.
• You have never used match and have no repo yet. Run match in setup mode instead.

Steps

1. Confirm the failure is decryption by running match in verbose mode and reading where it stops, after clone and before any portal call. Verify: the log shows clone success followed by a decrypt failure
2. Find the authoritative passphrase in the team secret manager or from the person who last ran match successfully, checking for trailing spaces or newline characters in the stored value. Verify: a candidate passphrase is identified and checked for stray whitespace
3. Provide it the way your setup expects: interactively on a workstation, or through the CI secret the match action reads. Verify: match proceeds past decryption to listing certificates, or fails identically which rules out delivery method
4. If it decrypts on one machine only, standardise: update the CI secret to that exact value and document where it lives without writing the value itself. Verify: CI and local match runs both decrypt successfully
5. If no copy works, accept the loss path: revoke the certificates in the Apple portal, delete the certs folder contents in the match repo, and run match to regenerate. Verify: new certificates are created, encrypted with a fresh passphrase and pushed to the repo
6. Store the new passphrase in the secret manager and note the rotation date in the team runbook. Verify: the runbook entry exists and a second team member confirms they can retrieve it
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

match encrypts certificates and profiles with OpenSSL using the passphrase as the only key. Apple cannot reset it and fastlane cannot recover it, by design, because the private keys must stay secret even from the git host. Mismatches usually come from CI secret drift, invisible whitespace, or a well-meaning rotation that updated one place but not the others.

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

fastlane match could not decrypt repo wrong passphrase

Passphrase-mismatch phrasing; locate the authoritative copy. 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.

match decrypt failed CI environment passphrase

CI-specific phrasing; check the secret value and whitespace. 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: OpenSSL version differences

Very old match repos encrypted with legacy defaults can fail on newer OpenSSL. Decrypt once on an older setup, then re-encrypt by re-running match. 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_GaMaiXMtaemojj1EjkMQ6Q

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

Thread query: fastlane match failed with error "couldn't decrypt the repo" using a passphrase

TL;DR: Use the exact passphrase the match repository was encrypted with, supplied through the match passphrase environment setting in CI or entered interactively, and confirm it against the machine that last updated the certificates. If the passphrase is truly lost, the stored certificates cannot be recovered: revoke them in the portal, clear the match repo, and regenerate with a new passphrase stored in the team secret manager. There is no bypass for the encryption.