The device refuses to install or launch the app: provisioning profile or code signature
A 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.
Fix it fast
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 - -2Match what you see, then jump to its fix
- 1
ProvisionedDevices does not contain the phone you are installing onThe device is not in the profileFix - 2
ExpirationDate is in the pastThe profile has expiredFix - 3
The certificate in DeveloperCertificates is not the Apple Development certificate you sign withThe app is signed with a certificate the profile does not listFix - 4
codesign lists an entitlement that is missing from the profile's EntitlementsThe app claims an entitlement the profile does not authorizeFix - 5
The profile checks out, but the phone refuses to run Xcode-built appsDeveloper Mode is off on the deviceFix
- 1
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.plist2Fix
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 > Register3Verify
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.plistConfirmed by developer.apple.com
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.plist2Fix
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 signing3Verify
The rebuilt app's profile shows a future ExpirationDate.
plutil -extract ExpirationDate raw -o - /tmp/profile.plistConfirmed by developer.apple.com
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.cer2Fix
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 on3Verify
Install the app again; the device accepts the signature.
codesign --verify --verbose MyApp.appConfirmed by developer.apple.com
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
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 devices2Fix
Turn on Developer Mode, restart when prompted, and confirm with the passcode after the restart.
# On the device: Settings > Privacy & Security > Developer Mode3Verify
Run the app from Xcode again.
xcrun devicectl list devicesConfirmed by developer.apple.com
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
Cannot change the App Privacy answers in App Store Connect
Publish Your App Privacy Responses?
Only the Account Holder, Admin and App Manager roles can answer the App Privacy questions.
2 causes, each with a fixMobile 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 fixMobile apps
You cannot find the button to pull your app back from review
No 'remove this version from review' message appears on the version page
There is no button called Reject Binary.
3 causes, each with a fixMobile apps
Your Apple Account cannot sign in to App Store Connect
Sign-in to App Store Connect is refused for an account that should have access
App Store Connect does not open to every Apple Account.
3 causes, each with a fixMobile apps
Apple rejected the app under Guideline 4.3, Design: Spam
Guideline 4.3(b) - Design - Spam
Guideline 4.3 is Apple's duplicate rule.
5 causes, each with a fixMobile apps
App Store Connect rejects a screenshot because it has transparency
Images can't include alpha channels or transparencies.
App Store Connect does not accept screenshots that carry an alpha channel or transparent pixels.
2 causes, each with a fix