-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
Can't build app with enabled Bridgeless mode on Android, but without can #45955
Comments
|
|
|
|
We need a reproducer to help you further @RustamHashymov |
@RustamHashymov For Android, you should not enable bridgeless mode alone, but you should modify the In 0.74, the New Architecture includes bridgeless enabled by default. |
@cipolleschi I mean here
If I try to build and bundle with |
@RustamHashymov please provide a reproducer project using this template: https://github.com/react-native-community/reproducer-react-native |
@RustamHashymov Yes, I know: Bridgeless is not supposed to be enabled in that way, in isolation. That setup will not work as it is not meant to work. To enable Bridgeless for Android you need to enable the New Architecture:
And it will work! That Boolean in the MainActivity is there if you want to disable Bridgeless after you enabled the New Architecture. |
@cipolleschi I forgot to mention that I have enabled it in my project and app runs successfully, but after I enable bridgeless, I can't run app and have that error. |
If you enabled the new architecture on 0.74, you don't have to enable also bridgeless. It is enabled by default. |
Description
Try to build and bundle app with bridgeless mode on Android. So build is succeeded and also bundle, but after it immediately error happen. Tried build and bundle without bridgeless mode, and it works fine.
Steps to reproduce
React Native Version
0.74.0
Affected Platforms
Runtime - Android, Build - MacOS
Areas
Bridgeless - The New Initialization Flow
Output of
npx react-native info
Reproducer
Screenshots and Videos
The text was updated successfully, but these errors were encountered: