How to Fix Xcode “The application could not be verified”

When Xcode tries to install an app on a physical iPhone or iPad, you may see The application could not be verified. The build can succeed while iOS rejects the app because its signing, provisioning, Bundle Identifier, entitlements, or device trust information cannot be validated correctly. This guide explains the most common causes and fixes.

What the error means

This message indicates an app-verification failure during installation or launch. The root cause is usually related to code signing or the relationship between the app, provisioning profile, development team, and target device.

The application could not be verified.

Common causes

• An incorrect or expired signing certificate
• A provisioning profile that does not match the app or device
• An existing app with the same Bundle Identifier but different signing
• Incorrect Signing & Capabilities settings
• Entitlements that do not match the provisioning configuration
• Developer Mode or trust problems
• An unsupported Xcode and iOS combination
• Stale build data

1. Remove the existing app

Delete the existing copy of the app from the iPhone or iPad, especially if the development team or signing certificate recently changed. Then use Product → Clean Build Folder in Xcode and run the app again.

2. Check Signing & Capabilities

Open Target → Signing & Capabilities and verify the selected Team, Bundle Identifier, signing certificate, and provisioning settings. If you use automatic signing, make sure Automatically manage signing is configured as intended.

3. Check the provisioning profile

For manual signing, confirm that the profile matches the Bundle Identifier, certificate, and target device. A development profile that does not include the device cannot be used for that device.

4. Check the certificate

Open Xcode Settings → Accounts and review the Apple ID and Team. Make sure the development certificate is valid and available on the Mac.

5. Check for a Bundle Identifier conflict

An App Store build or another development build using the same Bundle Identifier may be signed differently and may not be replaceable by the current build. When appropriate, use a separate development Bundle Identifier.

com.example.myapp
com.example.myapp.dev

6. Check entitlements

If the problem started after adding capabilities such as Push Notifications, iCloud, Associated Domains, or Keychain Sharing, verify that the app’s entitlements match the enabled capabilities and provisioning configuration.

7. Check Developer Mode and trust

Physical-device development on supported iOS versions requires Developer Mode. Make sure it is enabled when required and confirm that the device trusts the connected Mac.

8. Check Xcode and iOS compatibility

Verify that the installed Xcode version supports the iOS version on the device. Update Xcode if the device is running a newer unsupported iOS release.

9. Remove DerivedData

After correcting the underlying configuration, stale build data can occasionally keep the error around.

rm -rf ~/Library/Developer/Xcode/DerivedData/*

Restart Xcode, run Product → Clean Build Folder, and try again.

10. Reconnect the device

Quit Xcode, disconnect the device, restart both the Mac and the iPhone or iPad, reconnect them, and run the app again.

Summary

Xcode’s “The application could not be verified” error usually means iOS cannot validate the app’s signing or provisioning information. Start with the existing app on the device, then check Signing & Capabilities, the provisioning profile, certificate, Bundle Identifier, and entitlements. Also verify Developer Mode, Xcode/iOS compatibility, and the device connection.