Maaz Zindani

Loading the index…

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

The device refuses to install or launch the app: provisioning profile or code signature

ErrorA valid provisioning profile for this executable was not found.

Short answer

The device checks the embedded provisioning profile against the app: the profile must list the device, be unexpired, contain the signing certificate and authorize every entitlement the app claims. Unpack the profile from the built app with security cms and compare each of those four things, then fix the one that fails.

  • 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

    Unpack the profile embedded in the built app and read its expiry, devices and entitlements. Replace the path with your .app (inside the build products or the .xcarchive).

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

    1. 1ProvisionedDevices does not contain the phone you are installing onThe device is not in the profileFix
    2. 2ExpirationDate is in the pastThe profile has expiredFix
    3. 3The certificate in DeveloperCertificates is not the Apple Development certificate you sign withThe app is signed with a certificate the profile does not listFix
    4. 4codesign lists an entitlement that is missing from the profile's EntitlementsThe app claims an entitlement the profile does not authorizeFix
    5. 5The profile checks out, but the phone refuses to run Xcode-built appsDeveloper Mode is off on the deviceFix

What does the error look like?

  • A valid provisioning profile for this executable was not found.
  • Failed to verify code signature

Cause 1 of 5

The device is not in the profile

1Check

A development profile applies to a list of devices stored in ProvisionedDevices. A device outside the list cannot run the app. If the device was registered only recently, the identifier may also not be in profiles yet.

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

2Fix

In Signing & Capabilities turn on Automatically manage signing, pick your team, choose the device as the run destination, and click Register if the button appears. For a newly joined or renewed membership, wait for the registration processing the account help describes (up to 24 to 72 hours for 11 to 100 devices).

# Xcode > Signing & Capabilities > Automatically manage signing > Register

3Verify

Build again and unpack the new embedded profile; the device is now listed.

security cms -D -i MyApp.app/embedded.mobileprovision -o /tmp/profile.plist
plutil -extract ProvisionedDevices xml1 -o - /tmp/profile.plist

Confirmed by developer.apple.com

Did this fix it?

Cause 2 of 5

The profile has expired

1Check

Every profile has an ExpirationDate that limits how long it stays valid, typically not more than a year.

plutil -extract ExpirationDate raw -o - /tmp/profile.plist

2Fix

Let Xcode create a fresh development profile (Automatically manage signing on, team selected), or create a new profile on the Apple Developer website and select it in Signing & Capabilities, then rebuild.

# Xcode > Signing & Capabilities > Automatically manage signing

3Verify

The rebuilt app's profile shows a future ExpirationDate.

plutil -extract ExpirationDate raw -o - /tmp/profile.plist

Confirmed by developer.apple.com

Did this fix it?

Cause 3 of 5

The app is signed with a certificate the profile does not list

1Check

DeveloperCertificates holds the certificates of every developer allowed to sign code covered by the profile. Extract the first one and read its subject and dates.

plutil -extract DeveloperCertificates.0 raw -o - /tmp/profile.plist | base64 -D > /tmp/cert0.cer
certtool d /tmp/cert0.cer

2Fix

Sign with a certificate that is in the profile, or regenerate the profile so it includes your current certificate, then rebuild.

# Xcode > Settings > Apple Accounts, then rebuild with Automatically manage signing on

3Verify

Install the app again; the device accepts the signature.

codesign --verify --verbose MyApp.app

Confirmed by developer.apple.com

Did this fix it?

Cause 4 of 5

The app claims an entitlement the profile does not authorize

1Check

The profile's entitlements are an allowlist. Every entitlement the app claims must be in it, although the profile can allow more than the app uses. Compare the two lists.

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

2Fix

Remove the entitlement from the app's entitlements file, or add the matching capability to the app so a profile that authorizes it is generated, and rebuild.

# Xcode > Signing & Capabilities > + Capability (add the one that is missing)

3Verify

The two lists now match: nothing in codesign's output is absent from the profile.

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

Confirmed by developer.apple.com

Did this fix it?

Cause 5 of 5

Developer Mode is off on the device

1Check

A device with Developer Mode off cannot run apps from Xcode. The switch is under Settings > Privacy & Security and appears only after pairing starts.

xcrun devicectl list devices

2Fix

Turn on Developer Mode, restart when prompted, and confirm with the passcode after the restart.

# On the device: Settings > Privacy & Security > Developer Mode

3Verify

Run the app from Xcode again.

xcrun devicectl list devices

Confirmed by developer.apple.com

Did this fix it?

How do I stop it coming back?

  • Use Automatically manage signing for development builds so Xcode keeps the profile current.
  • Put a calendar reminder on certificate and profile expiry dates for distribution profiles.
  • Add capabilities in Signing & Capabilities rather than editing entitlements files by hand.

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.