Removing `newArchEnabled` property might cause issues with old libraries
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 127k
- Forks
- 25.3k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 4
Description
Description
When newArchEnabled property is set in gradle.properties, a warning is displayed:
********************************************************************************
WARNING: Setting `newArchEnabled=false` in your `gradle.properties` file is not
supported anymore since React Native 0.82.
You can remove the line from your `gradle.properties` file.
The application will run with the New Architecture enabled by default.
********************************************************************************
As long as your dependencies do not rely on this property to enable new arch, you are good to remove it. Libraries created with builder bob < v0.48.4, check for the property, so disabling it might cause issues with migration.
I propose to remove the line "You can remove the line from your gradle.properties file." or change it to mention old libraries.
Steps to reproduce
not relevant
React Native Version
0.82.0
Affected Platforms
Runtime - Android
Areas
Other (please specify)
Output of npx @react-native-community/cli info
not relevant
Stacktrace or Logs
not relevant
MANDATORY Reproducer
not relevant
Screenshots and Videos
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names gradle.properties and includes the warning text, but no React Native source file or test. Search the repository for the exact warning, inspect the Android configuration path that emits it, and compare the linked builder-bob template. Update the guidance for older libraries, then run the relevant Android configuration or warning test; done means the message no longer implies unconditional safety.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native
- Domain
- build-system, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100