Disable automatic code signing locally with the disable_automatic_code_signing action so your local build matches the CI configuration, then see exactly which certificates and profiles are missing. Make sure match can access its certificates repo from Bitrise (SSH key or token) and that the profiles are installed before the build step. Reproducing the CI signing setup locally is the fastest way to find the gap.

Context: Stack Overflow #48608664 (top answer, 7 votes): fastlane with match works locally but fails on Bitrise with missing certificates and provisioning profiles. The top answer explains why local success misleads: automatic signing hides which certificates Xcode actually uses, and the CI machine does not have them.

## Matched source
Source: Published skill
Original query: "Fastlane cannot find the provisioning profile on Bitrise"
Key terms: bitrise, cannot, fastlane, find, profile, provisioning