Repository navigation
Removing newArchEnabled property might cause issues with old libraries #54430
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
Activity
react-native-bot commentedon Nov 6, 2025
Warning
Missing reproducer: We could not detect a reproducible example in your issue report. Reproducers are mandatory and we can accept only one of those as a valid reproducer:
You can read more about about it on our website: How to report a bug.
cipolleschi commentedon Nov 6, 2025
@krizzu do you have a list of those libraries? @satya164 is there something we can do in Bob to improve the situation?
krizzu commentedon Nov 6, 2025
So just from my recent experience, react-native-pager-view and react-native-photo-manipulator has this issue, but there might be more.
Is it safe to always apply
com.facebook.reactplugin, even if old arch is enabled? If so, I think this would be easiest solution to apply to affected librariessatya164 commentedon Nov 6, 2025
we don't check for it anymore, so i guess codewise we don't have anything to do.
i think it's more about documenting the steps, we could add a FAQ entry for this and link to it in the error message on exactly what to do - which would be basically removing this check in the build gradle if the lib supports only new arch.
but if the lib supports both old and new architecture then i'm not sure what's the best way for them to check it during the build.
satya164 commentedon Nov 6, 2025
though on the otherhand, seems this warning is the app, so users can't actually do anything for library code with this check.
probably best to remove or rephrase "You can remove the line from your
gradle.propertiesfile." as @krizzu suggested to give time to library devs to update their code, after which it'll be ok to remove this.react-native-bot commentedon May 6, 2026
This issue is stale because it has been open for 180 days with no activity. It will be closed in 7 days unless you comment on it or remove the "Stale" label.
react-native-bot commentedon Nov 4, 2026
This issue is stale because it has been open for 180 days with no activity. It will be closed in 7 days unless you comment on it or remove the "Stale" label.
react-native-bot commentedon Nov 4, 2026
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.