-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
[0.74] Performing a refresh is unstable under Bridge Mode on Android (RNTester / New Arch) #43692
Labels
DX
Issues concerning how the developer experience can be improved.
Platform: Android
Android applications.
Type: New Architecture
Issues and PRs related to new architecture (Fabric/Turbo Modules)
Comments
huntie
added
Needs: Triage 🔍
Type: New Architecture
Issues and PRs related to new architecture (Fabric/Turbo Modules)
labels
Mar 28, 2024
github-actions
bot
added
Needs: Author Feedback
Needs: Repro
This issue could be improved with a clear list of steps to reproduce the issue.
labels
Mar 28, 2024
|
cortinico
added
DX
Issues concerning how the developer experience can be improved.
and removed
Needs: Triage 🔍
Needs: Author Feedback
Needs: Repro
This issue could be improved with a clear list of steps to reproduce the issue.
labels
Mar 28, 2024
cortinico
added a commit
to cortinico/react-native
that referenced
this issue
Apr 9, 2024
Summary: Currently NewArch-BridgeMode is partially broken when creating views via `ReactDelegate`. That's because we're using the ctor that doesn't account for `Boolean: fabricEnabled`. That means that the `RootView` that it will be created are all having setIsFabric(FALSE). This is causing problems like whitescreens on several reload + multiple warnings such as: ``` E com.facebook.react.bridge.ReactNoCrashSoftException: Cannot get UIManager because the context doesn't contain an active CatalystInstance. ``` Fixes facebook#43692 See for more context on this issues: facebook#43692 Changelog: [Android] [Fixed] - Fix bridge mode by constructing ReactDelegate correctly Reviewed By: cipolleschi Differential Revision: D55921078
This is indeed an issue, and the fix is here #43999 |
github-project-automation
bot
moved this from Inbox
to Done / Picked
in React Native 0.74 Releases
Apr 9, 2024
cortinico
added a commit
that referenced
this issue
Apr 9, 2024
Summary: Pull Request resolved: #43999 Currently NewArch-BridgeMode is partially broken when creating views via `ReactDelegate`. That's because we're using the ctor that doesn't account for `Boolean: fabricEnabled`. That means that the `RootView` that it will be created are all having setIsFabric(FALSE). This is causing problems like whitescreens on several reload + multiple warnings such as: ``` E com.facebook.react.bridge.ReactNoCrashSoftException: Cannot get UIManager because the context doesn't contain an active CatalystInstance. ``` Fixes #43692 See for more context on this issues: #43692 Changelog: [Android] [Fixed] - Fix bridge mode by constructing ReactDelegate correctly Reviewed By: cipolleschi Differential Revision: D55921078 fbshipit-source-id: 2c21d089a49538402d546177bcdb26c8d7d5fbc1
✅ Picked, this will land in 0.74 RC8 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
DX
Issues concerning how the developer experience can be improved.
Platform: Android
Android applications.
Type: New Architecture
Issues and PRs related to new architecture (Fabric/Turbo Modules)
Description
Performing a refresh is leading to some lifecycle error that results in a black screen.
Affects
0.74-stable
andmain
.Steps to reproduce
React Native Version
0.74.0, main
Affected Platforms
Runtime - Android
Areas
Bridgeless - The New Initialization Flow
Output of
npx react-native info
Stacktrace or Logs
Reproducer
https://github.com/facebook/react-native/tree/main/packages/rn-tester
Screenshots and Videos
Screen.Recording.2024-03-28.at.13.58.29.mov
The text was updated successfully, but these errors were encountered: