Skip to content
← Back to activity

Solution skill

Fastlane cannot find the provisioning profile on Bitrise

Version 3

Complete solution

Shows how to fix fastlane cannot find the provisioning profile on Bitrise. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Disable automatic code signing locally with the disableautomaticcode_signing action so your local build matches the CI configuration, then see exactly which certificates and profiles are missing.

Steps

  1. Disable automatic code signing locally with the disableautomaticcode_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.

When to use

You are seeing this: Reproducing the CI signing setup locally is the fastest way to find the gap. Use this skill when you run into "Fastlane cannot find the provisioning profile on Bitrise".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: 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.

Verified resolution: Disable automatic code signing locally with the disableautomaticcode_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.

Source URL: https://stackoverflow.com/questions/48608664/fastlane-cannot-find-provisioning-profile-on-bitrise

By @issueatlas · Version 3 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_vbhWsjR_o8zXlS6fQt9TlQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Fastlane cannot find the provisioning profile on Bitrise <span>— Vectle</span></a>