Repository navigation
☂️ Support Privacy Manifest and Required APIs in iOS and macOS #143232
Description
Activity
Plugin authors: follow issue #131940 for updates to our understanding of how this should work. #131940 (comment)
I might have a clue about the deadline. In an email that I received about an iOS application, Apple indicated
ITMS-90725: SDK version issue - This app was built with the iOS 16.4 SDK. Starting April 29, 2024, all iOS and iPadOS apps must be built with the iOS 17 SDK or later, included in XCode 15 or later, in order to be uploaded to be uploaded to App Store Connect or submitted for distribution.It also does not specify MacOS, so I think our idea of that is also correct? (although, it could also be incorrect since this was for an iOS app)
It also does not specify MacOS, so I think our idea of that is also correct? (although, it could also be incorrect since this was for an iOS app)
I had to specify it for a macOS and tvOS app so I believe this will come to all platforms Apple supports.
9 remaining items
I see many sub-issues here for modules and packages, but don't we need a doc for Flutter apps too?
Flutter apps are regular iOS/MacOS projects. You can add a Privacy Manifest to the Flutter app via XCode when the project is opened.
I know, and the same could be said for packages with ios plug-ins, right? They can just open the ios folder under xcode and add a privacy manifest, so why do they need special docs and apps don't?
- added a commit that references this issue
on May 22, 2024 We don't seem to have any "privacy manifest" docs on docs.flutter.dev for iOS or macOS. Should we add this for Q3?
Reacted by mono — Masayuki Ono, Natan Amorim Moraes, Brad Carson and Boby TanevWe don't seem to have any "privacy manifest" docs on docs.flutter.dev for iOS or macOS. Should we add this for Q3?
@stuartmorgan I know you've been thinking about writing something up, I took the liberty of filing flutter/website#10864 for plugin authors specifically, so @sfshaza2 can take over and/or track.
@stuartmorgan are you aware of any other work here, or can I close this?
We still have a few items left in the issue description checklist, so we should probably leave it open for now.
- added a commit that references this issue
on May 24, 2025 Dropping down to a P2 for the remaining work.
- added a commit that references this issue
on Jun 10, 2026 - added a commit that references this issue
on Jun 19, 2026
Umbrella issue to track the work to support privacy manifests (xcprivacy) across the engine, packages, 3p packages, tooling, etc.
From #131494:
Introduced in Xcode 15, Apple is now flagging specific APIs as needed a “Required Reason” to use. All usages of “Required Reason” APIs MUST be outlined in a Privacy manifest. A Privacy manifest is a document outlining how your app/SDK collects and uses a user’s data.
This is also time sensitive (https://developer.apple.com/news/?id=z6fu1dcu).
https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api
https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_data_use_in_privacy_manifests
https://developer.apple.com/videos/play/wwdc2023/10060/
Flutter.xcframeworkbundle #140934