Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[build-properties] Add field to enable/disable privacy manifest aggregation #28646

Merged
merged 3 commits into from
May 6, 2024

Conversation

brentvatne
Copy link
Member

@brentvatne brentvatne commented May 6, 2024

Why

There are a few issues right now with privacy manifest aggregation (facebook/react-native#44410, facebook/react-native#44402, facebook/react-native#44402) that I expect will be fixed in React Native 0.74.2, but in order to ensure that this doesn't break builds I've disabled it by default and added this build property to allow folks to toggle it on. We can switch on by default when 0.74.2 is released and proven to handle some edge cases better.

How

Same old process for adding a new property

Test Plan

Run tests

Checklist

@expo-bot expo-bot added the bot: suggestions ExpoBot has some suggestions label May 6, 2024
@expo-bot
Copy link
Collaborator

expo-bot commented May 6, 2024

Hi there! 👋 I'm a bot whose goal is to ensure your contributions meet our guidelines.

I've found some issues in your pull request that should be addressed (click on them for more details) 👇

⚠️ Suggestion: Missing changelog entries


Your changes should be noted in the changelog. Read Updating Changelogs guide and consider adding an appropriate entry to the following changelogs:


Generated by ExpoBot 🤖 against 14048c7

const { modResults: iosModResultsEnabled } = await compileMockModWithResultsAsync(
{},
{
plugin: withBuildProperties,
pluginProps: { ios: { ccache: true } },
pluginProps: { ios: { ccacheEnabled: true } },
Copy link
Member Author

Choose a reason for hiding this comment

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

this test looked incorrect, typechecking was failing on it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot: fingerprint compatible bot: suggestions ExpoBot has some suggestions published Changes from the PR have been published to npm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants