Skip to content

Conversation

@flutteractionsbot
Copy link

@flutteractionsbot flutteractionsbot commented Sep 23, 2024

This is the framework-side test for flutter/engine#55366. This test will fail unless it is run on a roll containing that fix.

Issue Link:

#154915

Changelog Description:

Test that a built macOS app contains the FlutterMacOS framework privacy manifest and validates flutter/engine#55366.

Impact Description:

Adds confidence the Flutter macOS engine framework contains the expected privacy manifest at the right path.

Workaround:

N/A

Risk:

What is the risk level of this cherry-pick?

  • Low
  • Medium
  • High

Test Coverage:

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

  • Yes
  • No

Validation Steps:

Run the flutter_tool tests

…155189)

Add tool test to validate a built macOS app contains the FlutterMacOS framework xcprivacy manifest.

Blocked on flutter/engine#55078 rolling in.
@flutteractionsbot flutteractionsbot added the cp: review Cherry-picks in the review queue label Sep 23, 2024
@flutteractionsbot
Copy link
Author

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

@github-actions github-actions bot added the tool Affects the "flutter" command-line tool. See also t: labels. label Sep 23, 2024
@itsjustkevin
Copy link
Contributor

@jmagman is this cherry-pick request still relevant?

@christopherfujino
Copy link
Contributor

@jmagman is this cherry-pick request still relevant?

Yes, I will follow up on it.

Copy link
Member

@jmagman jmagman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The path is actually incorrect and it was caught during beta codesigning #157016

This should be updated to #157136

Let's hold off on this stable PR until we confirm that framework test is passing on the beta branch.

@reidbaker
Copy link
Contributor

Not taking this for the hotfix release. Please message me if that is incorrect and we need to work to get this pr landed.

@christopherfujino
Copy link
Contributor

I am closing this as I believe this is obsolete and we already merged: 077c008 to the 3.27 branch.

@christopherfujino
Copy link
Contributor

I am closing this as I believe this is obsolete and we already merged: 077c008 to the 3.27 branch.

Whoops, I got mixed up, this is to 3.24

…on (flutter#157136)

The PrivacyInfo.xcprivacy file was originally copied to the top-level macOS framework, but instead needs to be in the Resources directory (which is a different path than iOS).  This caused codesigning issues flutter#157016.

The path is being corrected flutter/engine#55938 so update the framework test to handle either path.  It will be updated to just check the correct path once it rolls into the framework.
// the correct location is Versions/A/Resources/PrivacyInfo.xcprivacy.
// TODO(jmagman): Switch expectation to only check Resources/ once the new path rolls.
// https://github.com/flutter/flutter/issues/157016#issuecomment-2420786225
final File topLevelPrivacy = outputFlutterFramework.childFile('PrivacyInfo.xcprivacy');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WDYT @jmagman?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect, thank you!

@christopherfujino christopherfujino added the autosubmit Merge PR when tree becomes green via auto submit App label Oct 23, 2024
@auto-submit auto-submit bot removed the autosubmit Merge PR when tree becomes green via auto submit App label Oct 23, 2024
@auto-submit
Copy link
Contributor

auto-submit bot commented Oct 23, 2024

auto label is removed for flutter/flutter/155556, due to - The status or check suite Mac_arm64 tool_host_cross_arch_tests has failed. Please fix the issues identified (or deflake) before re-applying this label.

@christopherfujino
Copy link
Contributor

I'm confused by the test output of the failing test, however, it occurs that we will probably have to roll the engine this PR, or roll the engine into the upstream branch and then rebase this PR, until the updated test will pass.

@jmagman
Copy link
Member

jmagman commented Oct 23, 2024

I'm confused by the test output of the failing test, however, it occurs that we will probably have to roll the engine this PR, or roll the engine into the upstream branch and then rebase this PR, until the updated test will pass.

Oh right, the privacy manifest doesn't exist at all in the engine in stable. The engine roll should happen first.

auto-submit bot pushed a commit to flutter/engine that referenced this pull request Oct 23, 2024
### Issue Link:

flutter/flutter#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?

### Test Coverage:
Are you confident that your fix is well-tested by automated tests?

A test was added to the framework, which should also be cherry-picked flutter/flutter#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.
@github-actions github-actions bot added the engine flutter/engine related. See also e: labels. label Oct 24, 2024
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated this to include flutter/engine#56059

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh and post submits passed.

@reidbaker reidbaker added the autosubmit Merge PR when tree becomes green via auto submit App label Oct 24, 2024
@auto-submit auto-submit bot merged commit 6031040 into flutter:flutter-3.24-candidate.0 Oct 24, 2024
Copy link
Member

@cbracken cbracken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice!

@christopherfujino
Copy link
Contributor

LGTM

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Oct 24, 2024
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Oct 25, 2024
roondataten added a commit to roondataten/engine that referenced this pull request Dec 3, 2025
### Issue Link:

flutter/flutter#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?

### Test Coverage:
Are you confident that your fix is well-tested by automated tests?

A test was added to the framework, which should also be cherry-picked flutter/flutter#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.
bluemabatou added a commit to bluemabatou/engine that referenced this pull request Dec 4, 2025
### Issue Link:

flutter/flutter#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?

### Test Coverage:
Are you confident that your fix is well-tested by automated tests?

A test was added to the framework, which should also be cherry-picked flutter/flutter#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.
januaryetherum added a commit to januaryetherum/engine that referenced this pull request Dec 9, 2025
### Issue Link:

flutter/flutter#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?

### Test Coverage:
Are you confident that your fix is well-tested by automated tests?

A test was added to the framework, which should also be cherry-picked flutter/flutter#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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autosubmit Merge PR when tree becomes green via auto submit App cp: review Cherry-picks in the review queue engine flutter/engine related. See also e: labels. tool Affects the "flutter" command-line tool. See also t: labels.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants