Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

App Store Connect emails ITMS-91061 for a Flutter iOS app

ErrorITMS-91061: Missing privacy manifest

Short 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.

  • Applies to Flutter 3.3x stable, Xcode 26, iOS 18 and 26
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 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"
  2. 2Match what you see, then jump to its fix

    1. 1The 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. 2The path in the mail is Frameworks/Flutter.framework/FlutterThe email names Flutter.framework itselfFix
    3. 3The 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

What does the error look like?

  • ITMS-91061: Missing privacy manifest
  • Your 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.lock

2Fix

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 clean

3Verify

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

Did this fix it?

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 --version

2Fix

Upgrade the Flutter SDK on your channel and rebuild.

flutter upgrade
flutter clean

3Verify

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

Did this fix it?

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.lock

2Fix

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

Did this fix it?

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:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.