When you upload an app from Xcode to App Store Connect or run Validate App from an Archive, Xcode may report App validation failed. This message is usually a summary rather than the root cause. It means one or more App Store validation checks failed, such as code signing, Bundle ID, version information, app icons, entitlements, embedded frameworks, or extensions.
Common causes
- The Signing & Capabilities settings do not match the provisioning profile.
- The Bundle Identifier does not match the App ID registered in App Store Connect.
- The version or build number is invalid or has already been used.
- Required resources such as app icons are missing or invalid.
- The app contains unsupported or incorrectly configured entitlements.
- An embedded framework or extension has an invalid Bundle ID, signature, or deployment target.
- Required Info.plist keys are missing or contain invalid values.
- The Archive contains an invalid binary or incorrectly signed component.
Typical error output
App validation failed
Validation failed
Invalid Bundle
Invalid Code Signing Entitlements
Missing required icon fileIn most cases, Xcode shows a more specific validation message near the generic “App validation failed” line. That detailed message is the one you should troubleshoot first.
How to identify the problem
- Open Window > Organizer in Xcode.
- Select the relevant Archive and run Validate App or Distribute App.
- Read the detailed validation messages shown together with “App validation failed”.
- Check the target’s Signing & Capabilities, General, and Build Settings.
- Compare the Bundle ID, version, and build number with the app record in App Store Connect.
Fix 1: Check code signing
Verify the Team, Bundle Identifier, signing certificate, and provisioning profile under Signing & Capabilities. If you use automatic signing, enable Automatically manage signing, select the correct Team, and create a new Archive.
Extensions such as widgets and notification service extensions have their own Bundle IDs and signing requirements. Check each target, not only the main app target.
Fix 2: Check the Bundle ID and version/build numbers
Make sure PRODUCT_BUNDLE_IDENTIFIER matches the Bundle ID registered for the app in App Store Connect. Also increase the build number if that build has already been uploaded.
Marketing Version: 1.2.0
Build: 15Fix 3: Check Info.plist and required resources
Review the app icon set, supported devices, display name, and required usage-description keys. If the app uses protected resources such as the camera, photo library, or location services, confirm the related usage descriptions are present and accurate.
Fix 4: Inspect the Archive and code signing
Check whether frameworks and extensions embedded in the Archive are signed correctly. You can inspect a built app with the macOS codesign command.
codesign -dv --verbose=4 /path/to/YourApp.appTo inspect the app’s entitlements, use:
codesign -d --entitlements :- /path/to/YourApp.appFix 5: Clean and create a new Archive
After correcting the configuration, do not reuse the old Archive. Create a new one. If Xcode appears to be using stale build data, you can also remove DerivedData and rebuild.
rm -rf ~/Library/Developer/Xcode/DerivedData/*Important notes
“App validation failed” is not usually the root cause. Avoid changing random signing or build settings based only on that final line. Find the specific validation error shown with it and fix that issue first.
App Store validation requirements can change over time. If the error starts after updating Xcode or after an App Store requirement change, compare the current Xcode validation details with any warnings shown in App Store Connect.
Summary
When Xcode reports “App validation failed,” start with the detailed validation message, then check code signing, Bundle ID, version/build numbers, Info.plist, app icons, entitlements, frameworks, and extensions. After fixing the underlying issue, create a fresh Archive and run Validate App again before uploading.
