App Store Connect emails ITMS-91061 for a Flutter iOS app
ITMS-91061: Missing privacy manifestShort answer
ITMS-91061 means a framework inside your app is on Apple's list of commonly used SDKs and has no privacy manifest. The mail names the framework. The manifest has to come from that SDK, so update the Flutter plugin or the Flutter SDK that brings it in, rebuild the archive, and upload again.
Fix it fast
1Find out which cause you have
Read the framework path in Apple's email, then build the archive and list which frameworks in it carry a privacy manifest. The framework named in the mail is the one missing from that list.
flutter build ipa find build/ios/archive -name "PrivacyInfo.xcprivacy"2Match what you see, then jump to its fix
- 1
The email names a plugin or SDK framework, for example Frameworks/FirebaseCore.framework or another package from your pubspecA Flutter plugin pulls in an SDK version without a manifestFix - 2
The path in the mail is Frameworks/Flutter.framework/FlutterThe email names Flutter.framework itselfFix - 3
The previous release uploaded fine and you added or switched a plugin sinceThis release added a listed SDK, so the check fired for the first timeFix
- 1
What does the error look like?
ITMS-91061: Missing privacy manifestYour app includes "Frameworks/FirebaseCore.framework/FirebaseCore", which includes FirebaseCore, an SDK that was identified in the documentation as a commonly used third-party SDK.Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest.
Cause 1 of 3
A Flutter plugin pulls in an SDK version without a manifest
1Check
See which plugins are behind their latest release. A plugin that bundles an old native SDK keeps the old, manifest-less framework.
dart pub outdated
grep -n "firebase_core" pubspec.lock2Fix
Upgrade the plugin that owns the framework, so it brings a newer SDK that includes the manifest. Then clean the build so the iOS pods are resolved again.
dart pub upgrade firebase_core
flutter clean3Verify
Build the archive again and look for the manifest inside the framework named in the email.
flutter build ipa
find build/ios/archive -path "*FirebaseCore*" -name "PrivacyInfo.xcprivacy"Confirmed by developer.apple.com
Cause 2 of 3
The email names Flutter.framework itself
1Check
Apple's list of SDKs that need a manifest includes Flutter. An old Flutter SDK builds an engine framework without it.
flutter --version2Fix
Upgrade the Flutter SDK on your channel and rebuild.
flutter upgrade
flutter clean3Verify
Build again and check the archive for the manifest.
flutter build ipa
find build/ios/archive -path "*Flutter.framework*" -name "PrivacyInfo.xcprivacy"Confirmed by developer.apple.com
Cause 3 of 3
This release added a listed SDK, so the check fired for the first time
1Check
Apple applies the rule to a new app that includes a listed SDK, or to an update that adds one. Compare the lock file against the last released tag.
git diff <last-release-tag> -- pubspec.lock2Fix
For the new plugin, use a release whose native SDK ships a manifest. If none exists, ask the plugin's maintainer, since the manifest has to come from the SDK.
dart pub upgrade <new_plugin>3Verify
The archive lists a manifest for that framework, and App Store Connect accepts the upload.
find build/ios/archive -name "PrivacyInfo.xcprivacy"Confirmed by developer.apple.com
How do I stop it coming back?
- Run dart pub outdated before each release and upgrade plugins that wrap Firebase, Google or other listed SDKs.
- Check the archive for PrivacyInfo.xcprivacy files before every upload.
- Read Apple's SDK list when adding a plugin that wraps a large native SDK.
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?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- Dispatch ProA real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
- Qist BazaarA buy-now-pay-later marketplace built from a blank repo, now past 100K downloads on Google Play.
Related fixes
Mobile apps
Xcode archive or upload says there is no privacy manifest
Archive does not contain any PrivacyInfo.xcprivacy files
Your app target does not contain a PrivacyInfo.xcprivacy file, or the file is there but is not packaged into the product.
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
pod install cannot pick a version of a pod that satisfies every requirement
Specs satisfying the `FirebaseAuth (~> 11.0)` dependency were found, but they required a higher minimum deployment target.
CocoaPods tried every version of the named pod and none fit all requirements.
4 causes, each with a fixMobile apps
flutter run says: Could not run Runner.app, try Xcode Product > Run
Try launching Xcode and selecting "Product > Run" to fix the problem:
Flutter prints this when installing or launching the built app on the iPhone fails, and it hides the real reason.
4 causes, each with a fixMobile apps
flutter doctor says CocoaPods is installed but not working
You appear to have CocoaPods installed but it is not working.
Flutter runs pod --version and treats a failed or unreadable result as a broken install.
3 causes, each with a fixMobile apps
flutter run on iOS or macOS stops with Error running pod install
Warning: CocoaPods not installed. Skipping pod install.
Flutter only reports that pod install failed; the reason is in the lines just above it.
5 causes, each with a fix