You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Apps that use MediaPipe via Swift Package Manager cannot be uploaded to App Store Connect / TestFlight #6367
Installed using virtualenv? pip? Conda?(if python)
No response
MediaPipe version
No response
Bazel version
No response
XCode and Tulsi versions (if iOS)
No response
Android SDK and NDK versions (if android)
No response
Android AAR (if android)
None
OpenCV version (if running on desktop)
No response
Describe the problem
Apps that consume MediaPipe Tasks through Swift Package Manager cannot be uploaded to App Store Connect / TestFlight.
Upload validation fails with:
This bundle Payload/<App>.app/Frameworks/MediaPipeTasksAudio.framework is invalid. The Info.plist file is missing the required key: CFBundleVersion. (90056)
The Info.plist inside each framework of the 1.0.1 xcframeworks referenced by Package.swift has no CFBundleVersion. The frameworks are static, but Xcode still copies every SPM binary-target framework into <App>.app/Frameworks/ (as a small stub binary plus the framework's original Info.plist), so the incomplete plist ships in the ipa and App Store validation rejects it. The app builds, signs and runs fine. The failure only appears at upload.
Steps to reproduce
Add the package by revision and depend on the MediaPipeTasksVision product only.
Archive an iOS app and export with the app-store method.
Upload with altool / Transporter / fastlane upload_to_testflight.
Validation fails with error 90056 on MediaPipeTasksAudio.framework.
Complete Logs
This bundle Payload/<App>.app/Frameworks/MediaPipeTasksAudio.framework is invalid.
The Info.plist file is missing the required key: CFBundleVersion. (90056)
changed the title [-]Apps that consume MediaPipe via Swift Package Manager cannot be uploaded to App Store Connect / TestFlight[/-][+]Apps that use MediaPipe via Swift Package Manager cannot be uploaded to App Store Connect / TestFlight[/+]on Sep 19, 2026
This occurs because Xcode copies the Info.plist from the framework into the app bundle, even for static frameworks, and App Store Connect requires these keys for all embedded frameworks.
A reliable workaround is to add a custom build phase script to your Xcode project to inject the missing keys into the relevant Info.plist files right before code signing.
Steps to apply the workaround:
Ensure you are on the right branch: If Xcode fails to find Package.swift when adding the dependency, make sure your Dependency Rule is set to Branch and you type master.
Go to your app target's Build Phases.
Add a new Run Script Phase and drag it to the very bottom of the list.
Paste the following script:
#!/bin/bash
# Use CODESIGNING_FOLDER_PATH to reliably point to the .app bundle being archived
APP_PLIST="${CODESIGNING_FOLDER_PATH}/Info.plist"
# Fetch versions from the main app's Info.plist (with fallbacks)
APP_BUNDLE_VERSION=$(/usr/libexec/PlistBuddy -c "Print CFBundleVersion" "$APP_PLIST" 2>/dev/null || echo "1")
APP_SHORT_VERSION=$(/usr/libexec/PlistBuddy -c "Print CFBundleShortVersionString" "$APP_PLIST" 2>/dev/null || echo "1.0")
# Iterate through MediaPipe frameworks in the final app bundle and inject the keys
if [ -d "${CODESIGNING_FOLDER_PATH}/Frameworks" ]; then
find "${CODESIGNING_FOLDER_PATH}/Frameworks" -type d -name "MediaPipe*.framework" | while read -r FRAMEWORK_PATH; do
INFO_PLIST="${FRAMEWORK_PATH}/Info.plist"
if [ -f "$INFO_PLIST" ]; then
# Inject CFBundleVersion
/usr/libexec/PlistBuddy -c "Add CFBundleVersion string $APP_BUNDLE_VERSION" "$INFO_PLIST" 2>/dev/null || \
/usr/libexec/PlistBuddy -c "Set CFBundleVersion $APP_BUNDLE_VERSION" "$INFO_PLIST"
# Inject CFBundleShortVersionString
/usr/libexec/PlistBuddy -c "Add CFBundleShortVersionString string $APP_SHORT_VERSION" "$INFO_PLIST" 2>/dev/null || \
/usr/libexec/PlistBuddy -c "Set CFBundleShortVersionString $APP_SHORT_VERSION" "$INFO_PLIST"
fi
done
fi
Important for Xcode 15+: Go to your target's Build Settings, search for User Script Sandboxing (ENABLE_USER_SCRIPT_SANDBOXING), and set it to No. If this is left on, Xcode will silently block the script from modifying the framework files.
Please test if this setup resolves your issue, Thank You
Thanks for the suggestion @HarishPermal! The script worked with a few edits: I had to re-sign each framework in order to get it installed on a physical device and I needed to take the version from build settings since the script would run before the Info.plist was written on a clean run. Here's what I ended up with:
if [ -z "${CURRENT_PROJECT_VERSION}" ] || [ -z "${MARKETING_VERSION}" ]; then
echo "error: CURRENT_PROJECT_VERSION and MARKETING_VERSION must be set to stamp the MediaPipe framework plists"
exit 1
fi
set_plist_key() {
/usr/libexec/PlistBuddy -c "Add $1 string $2" "$3" 2>/dev/null ||
/usr/libexec/PlistBuddy -c "Set $1 $2" "$3"
}
for FRAMEWORK_PATH in "${CODESIGNING_FOLDER_PATH}"/Frameworks/MediaPipe*.framework; do
[ -d "$FRAMEWORK_PATH" ] || continue
INFO_PLIST="${FRAMEWORK_PATH}/Info.plist"
set_plist_key CFBundleVersion "$CURRENT_PROJECT_VERSION" "$INFO_PLIST"
set_plist_key CFBundleShortVersionString "$MARKETING_VERSION" "$INFO_PLIST"
for KEY in CFBundleVersion CFBundleShortVersionString; do
if ! /usr/libexec/PlistBuddy -c "Print $KEY" "$INFO_PLIST" >/dev/null 2>&1; then
echo "error: $KEY is still missing from $INFO_PLIST ($(ls -l "$INFO_PLIST"))"
exit 1
fi
done
# Xcode signs each framework as it copies it, before this phase runs, and Info.plist is sealed by that signature
if [ "${CODE_SIGNING_ALLOWED}" = "YES" ] && [ -n "${EXPANDED_CODE_SIGN_IDENTITY}" ]; then
/usr/bin/codesign --force --sign "${EXPANDED_CODE_SIGN_IDENTITY}" ${OTHER_CODE_SIGN_FLAGS:-} --timestamp=none --generate-entitlement-der "$FRAMEWORK_PATH" || exit 1
fi
done
FWIW, my original workaround was to delete the framework stubs in a trailing build phase script.
Activity
[-]Apps that consume MediaPipe via Swift Package Manager cannot be uploaded to App Store Connect / TestFlight[/-][+]Apps that use MediaPipe via Swift Package Manager cannot be uploaded to App Store Connect / TestFlight[/+]HarishPermal commentedon Sep 21, 2026
Hi @mikeg0184,
This occurs because Xcode copies the
Info.plistfrom the framework into the app bundle, even for static frameworks, and App Store Connect requires these keys for all embedded frameworks.A reliable workaround is to add a custom build phase script to your Xcode project to inject the missing keys into the relevant Info.plist files right before code signing.
Steps to apply the workaround:
Package.swiftwhen adding the dependency, make sure your Dependency Rule is set to Branch and you type master.Important for Xcode 15+: Go to your target's Build Settings, search for User Script Sandboxing (ENABLE_USER_SCRIPT_SANDBOXING), and set it to No. If this is left on, Xcode will silently block the script from modifying the framework files.
Please test if this setup resolves your issue, Thank You
mikeg0184 commentedon Sep 21, 2026
Thanks for the suggestion @HarishPermal! The script worked with a few edits: I had to re-sign each framework in order to get it installed on a physical device and I needed to take the version from build settings since the script would run before the Info.plist was written on a clean run. Here's what I ended up with:
FWIW, my original workaround was to delete the framework stubs in a trailing build phase script.