When uploading an app from Xcode to App Store Connect, you may encounter an “Invalid Bundle” error during validation, upload, or processing. This usually means that the app bundle, an embedded framework, an extension, Info.plist, or the signing configuration does not meet App Store Connect requirements.
Common causes
- Required Info.plist keys or values are invalid
- Bundle identifiers are inconsistent across targets
- A framework or app extension is embedded incorrectly
- Signing, provisioning profiles, and entitlements do not match
- The bundle contains unexpected executables, symlinks, macOS-only files, or other unsupported content
- Version values such as CFBundleVersion or CFBundleShortVersionString are invalid
Typical situations
The archive itself may succeed, but App Store Connect can still reject it during validation, upload, or processing. If the detailed message names a specific framework, extension, bundle, or Info.plist key, start with that item first.
How to diagnose the problem
- Open the affected archive in Xcode Organizer and inspect the full validation or upload message.
- Identify the bundle, framework, extension, or plist key mentioned in the error.
- Review General, Signing & Capabilities, and Build Settings for each relevant target.
- Inspect the archived .app bundle and check for duplicate or unexpected files.
You can right-click the archive or app in Finder, choose “Show Package Contents,” and inspect the files under Products/Applications/YourApp.app.
Solution 1: Check Info.plist values
Verify the bundle identifier, version, display name, supported platforms, and other required values. If Info.plist is maintained manually, also check each value type.
CFBundleIdentifier = $(PRODUCT_BUNDLE_IDENTIFIER)
CFBundleShortVersionString = $(MARKETING_VERSION)
CFBundleVersion = $(CURRENT_PROJECT_VERSION)Solution 2: Fix bundle identifiers
The main app and every app extension must use valid, unique bundle identifiers registered for the correct Apple Developer team. Extensions normally use a separate identifier derived from the main app identifier.
com.example.myapp
com.example.myapp.shareextensionSolution 3: Review embedded frameworks
In the target’s General tab, check Frameworks, Libraries, and Embedded Content. Dynamic frameworks generally need the appropriate embedding option such as Embed & Sign, while static libraries should not be unnecessarily embedded. Remove duplicate framework entries if present.
Solution 4: Review code signing
Under Signing & Capabilities, make sure the Team, Bundle Identifier, provisioning profile, certificate, and entitlements all match. If you use automatic signing, confirm that Automatically manage signing is enabled as intended and let Xcode refresh the required signing assets.
Solution 5: Clean and create a new archive
After changing bundle or signing settings, create a fresh archive instead of reusing an older one.
rm -rf ~/Library/Developer/Xcode/DerivedData/*Then run Product → Clean Build Folder in Xcode and archive the project again.
Important notes
“Invalid Bundle” is a broad error. The most useful information is usually in the detailed message that follows it. Pay close attention to the exact bundle name, framework, extension, or key that App Store Connect reports. Also avoid manually embedding a dependency twice when it is already managed by CocoaPods or Swift Package Manager.
Summary
App Store Connect’s “Invalid Bundle” error is commonly caused by problems with Info.plist, bundle identifiers, embedded frameworks, app extensions, signing, or version metadata. Identify the exact bundle mentioned in the detailed error, correct the related settings, clean the project, and create a new archive before uploading again.
