-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Adding Expo modules to a bare React Native app disables concurrent features. #25024
Comments
Thank you for filing this issue! |
Hi @Kudo, did you have time to look at this issue? Thanks in advance 🙏 |
# Why fixes #25024 close ENG-10499 # How i missed aligning the ReactActivityDelegate changes during react native upgrade. this pr tried to fill the `launchOptions` from `composeLaunchOptions()` as upstream: https://github.com/facebook/react-native/blob/5029cef0a99469e37bc2f4d72ca2e1f3d6791511/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/ReactActivityDelegate.java#L102-L109 # Test Plan test repro from #25024
…#25415) # Why fixes expo#25024 close ENG-10499 # How i missed aligning the ReactActivityDelegate changes during react native upgrade. this pr tried to fill the `launchOptions` from `composeLaunchOptions()` as upstream: https://github.com/facebook/react-native/blob/5029cef0a99469e37bc2f4d72ca2e1f3d6791511/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/ReactActivityDelegate.java#L102-L109 # Test Plan test repro from expo#25024
I think this problem still persists in react-native version 0.74 and expo sdk 51.0.0-preview.3 |
Minimal reproducible example
https://github.com/ahmetbicer/expo-modules-concurrent-root-issue
Summary
After adding Expo modules to a bare React Native app with new arch enabled,
concurrentRoot: true
disappears, and React 18 features, such as automatic batching, are not working. This issue is observed only in Android; iOS works as expected.Steps to Reproduce:
npx react-native@latest init ConcurrentRootTest
newArchEnabled
flag totrue
in gradle.properties.concurrentRoot: true
in metro logsnpx install-expo-modules@latest
concurrentRoot: true
disappears and react 18 features such as automatic batching are not working.Expected Behavior:
The concurrentRoot: true property should persist even after Expo modules are added.
Environment
expo-env-info 1.0.5 environment info:
System:
OS: macOS 13.5.2
Shell: 5.9 - /bin/zsh
Binaries:
Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 8.1.0 - ~/.nvm/versions/node/v16.13.0/bin/npm
Watchman: 2023.07.24.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.12.1 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
IDEs:
Android Studio: 2022.3 AI-223.8836.35.2231.10406996
Xcode: 14.3.1/14E300c - /usr/bin/xcodebuild
npmPackages:
expo: ^49.0.0 => 49.0.16
react: 18.2.0 => 18.2.0
react-native: 0.72.6 => 0.72.6
Expo Workflow: bare
The text was updated successfully, but these errors were encountered: