Home › Build error fixes › iOS / Xcode

Provisioning profile does not contain your signing certificate

iOS / Xcode · last reviewed 2026-11-10

The error looks like this

error: Provisioning profile "com.acme AppStore" doesn't include signing certificate "Apple Distribution: Acme (X1)".

Why it happens

The profile was generated for a different (often expired or revoked) certificate than the one in your keychain.

How to fix it

  1. developer.apple.com > Profiles: edit the profile, tick the current Distribution certificate, regenerate and download it.
  2. Double-click the new .mobileprovision (or Xcode > Settings > Accounts > Download Manual Profiles).
  3. If using fastlane match: run fastlane match appstore --force to regenerate.
  4. Make sure every target (including extensions) uses the same signing style.

Not sure this is your error? Let ReleaseMedic read the whole log

Build logs are long and the last line is rarely the real cause. ReleaseMedic finds the first real error, explains it and gives the steps — free, and the log never leaves your computer.

$ npx releasemedic log build.log

Or pipe a build straight in: cd android && ./gradlew bundleRelease 2>&1 | npx releasemedic log -

Catch it before you build

Most release errors come from project settings you can check in seconds — signing, SDK levels, privacy manifests, permissions, push and login setup.

$ npx releasemedic

Related iOS / Xcode errors