Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Xcode says the provisioning profile does not match the entitlements file's application-identifier

ErrorProvisioning profile doesn't match the entitlements file's value for the application-identifier entitlement

Short answer

The app is claiming an App ID or entitlement that the provisioning profile does not allow. Dump the entitlements in the signed app and the allowlist in the profile, then compare. Either the bundle ID falls outside the profile's App ID, or an entitlement is missing from the profile. Fix the bundle ID, or regenerate the profile.

  • Applies to Xcode 26, iOS 26, macOS 26
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Look at both sides of the comparison. The first command prints what the built app claims. The second prints the App ID the embedded profile allows. Run them on the same .app.

    codesign --display --entitlements - --xml MyApp.app | plutil -convert xml1 -o - -
    security cms -D -i MyApp.app/embedded.mobileprovision -o /tmp/profile.plist
    plutil -extract Entitlements.application-identifier raw -o - /tmp/profile.plist
  2. 2Match what you see, then jump to its fix

    1. 1The application-identifier claimed by the app (team prefix plus bundle ID) is not the profile's App ID, and does not start with the profile's wildcard prefixThe bundle ID is outside the App ID in the profileFix
    2. 2The app's entitlements include a key (for example keychain-access-groups or an application group) that is missing from the profile's EntitlementsThe app claims an entitlement the profile does not listFix

What does the error look like?

  • Provisioning profile doesn't match the entitlements file's value for the application-identifier entitlement

Cause 1 of 2

The bundle ID is outside the App ID in the profile

1Check

The application-identifier entitlement is an App ID made of a prefix and a bundle ID. A profile for an explicit App ID matches only that bundle ID. A wildcard profile matches any App ID that begins with its prefix. Compare the value printed by the first-step commands with the bundle ID in your target.

plutil -extract Entitlements.application-identifier raw -o - /tmp/profile.plist
grep -n PRODUCT_BUNDLE_IDENTIFIER MyApp.xcodeproj/project.pbxproj

2Fix

Make the bundle ID match the profile (or the profile match the bundle ID). With manual signing, pick a profile created for this exact App ID. With automatic signing, set the correct team and bundle ID in Signing & Capabilities and let Xcode create the profile.

# Target > Build Settings
PRODUCT_BUNDLE_IDENTIFIER = com.example.myapp

3Verify

Build again and dump the entitlements of the new app. The application-identifier should start with the profile's prefix.

codesign --display --entitlements - --xml MyApp.app | plutil -convert xml1 -o - -

Confirmed by developer.apple.com

Did this fix it?

Cause 2 of 2

The app claims an entitlement the profile does not list

1Check

The profile's Entitlements dictionary is an allowlist. Every entitlement the app claims must be in it. It is fine for the profile to allow more than the app uses, but never less. Print the allowlist and compare it with the app's list.

plutil -extract Entitlements xml1 -o - /tmp/profile.plist
codesign --display --entitlements - --xml MyApp.app | plutil -convert xml1 -o - -

2Fix

Either remove the entitlement from your .entitlements file, or add the capability to the App ID and regenerate the profile so the allowlist includes it. In Xcode this means adding the capability in Signing & Capabilities with automatic signing on, so the profile is refreshed.

# Xcode: target > Signing & Capabilities > + Capability

3Verify

Rebuild and run the two dump commands again. Every key in the app's list must appear in the profile's list.

plutil -extract Entitlements xml1 -o - /tmp/profile.plist

Confirmed by developer.apple.com

Did this fix it?

How do I stop it coming back?

  • Change the bundle ID and the capabilities in one commit, then check Signing & Capabilities straight after.
  • Keep a wildcard profile out of apps that need capabilities. Use an explicit App ID for each shipping app.
  • Check the entitlements of an archive before you upload it, with the same codesign command.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Related fixes

Mobile apps

App record creation fails because you lack permission

You cannot add a new app in App Store Connect as a Developer or limited user

Only the Account Holder, an Admin or an App Manager can create an app record, and Apple blocks it until the Account Holder has signed the latest agreement.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.