[CP-stable]Add xcprivacy privacy manifest to macOS framework

[flutteractionsbot]

Issue Link:

https://github.com/flutter/flutter/issues/154915

Changelog Description:

Comply with the new Apple privacy manifest policy for the macOS Flutter engine framework and prevent the "Missing privacy manifest" warning when submitting a macOS app to the App Store.

Impact Description:

The macOS App Store will start enforcing privacy manifests for third-party SDKs starting November 12, 2024. This change adds an empty privacy manifest to the Flutter engine FlutterMacOS.framework to comply with this new policy and prevents the warning.

Workaround:

Add an empty PrivacyInfo.xcprivacy plist to FlutterMacOS.framework and re-codesign it manually.

Risk:

What is the risk level of this cherry-pick?

• [x] Low
• [ ] Medium
• [ ] High

Test Coverage:

Are you confident that your fix is well-tested by automated tests?

• [ ] Yes
• [x] No

A test was added to the framework, which should also be cherry-picked https://github.com/flutter/flutter/pull/155556. While we can confirm the expected file is present, only a TestFlight/App Store submission will confirm the warning is gone.

Validation Steps:

Submit a Flutter macOS app to TestFlight or the App Store. Confirm there is no submission warning email sent.

[flutteractionsbot]

@jmagman please fill out the PR description above, afterwards the release team will review this request.

[bobin-abraham]

Hi Team,

I am still able to reproduce this issue . I am using the Flutter version "Channel stable, 3.27.4, on macOS 15.1.1 24B91 darwin-arm64, locale en-IN) .

On every MacOS build released for either Beta testing or App Store is making the warning email.

Adding the warning email content for your reference

"ITMS-91061: Missing privacy manifest - Your app includes “Contents/Frameworks/FlutterMacOS.framework/Versions/A/FlutterMacOS”, which includes Flutter, an SDK that was identified in the documentation as a commonly used third-party SDK. Starting February 12, 2025, if a new app includes a commonly used third-party SDK, or an app update adds a new commonly used third-party SDK, the SDK must include a privacy manifest file or you won’t be able to submit the app for review in App Store Connect. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements."

Please fix this issues ASAP, because the last date is Feb 12th

[stuartmorgan-g]

@bobin-abraham Please file issues in the issue tracker.

[chengxuyuanzzy]

@bobin-abraham Has it been solved?

[bobin-abraham]

@chengxuyuanzzy Yes the issue is solved. We upgraded Connectivity_plus to version 6.1.3 .

After that we released few builds to App Store and none of them got any warnings.