react-native: [Android] - Release Application crashes immediately after having upgraded to 0.70.0 with newArchEnabled=true
Description
Application crashes immediately after having upgraded to 0.70.0 with newArchEnabled=true
. If i keep newArchEnabled=false
the app works correctly.
Version
0.70.0
Output of npx react-native info
System:
OS: macOS 12.5.1
CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Memory: 158.54 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm
Watchman: 2022.09.05.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK: Not Found
IDEs:
Android Studio: 4.1 AI-201.8743.12.41.6953283
Xcode: 13.4.1/13F100 - /usr/bin/xcodebuild
Languages:
Java: 11.0.16 - /Library/Java/JavaVirtualMachines/jdk-11.0.16.jdk/Contents/Home/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.1.0 => 18.1.0
react-native: 0.70.0 => 0.70.0
react-native-macos: Not Found
npmGlobalPackages:
*react-native*: Not Found
Steps to reproduce
./gradlew assembleRelease --no-daemon --max-workers 2
Snack, code example, screenshot, or link to a repository
none
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 5
- Comments: 19 (7 by maintainers)
Commits related to this issue
- Fix Android release version launch crash https://github.com/facebook/react-native/issues/34684#issuecomment-1350237123 — committed to denkeni/CCWatch by denkeni a year ago
Still have this error after upgrading to react-native 0.70.4
I spent half of the day trying different solutions. In the end managed it by changing classpath(“com.android.tools.build:gradle:7.3.1”) to classpath(“com.android.tools.build:gradle:7.2.2”)
Closing as we got no repros and we weren’t able to pinpoint the root cause here. Please open a new issue, provide a repro and we can look into it
I would suggest opening an issue on Reanimated issue tracker as they probably know more what’s happening here. Having a reproducer with just Reanimated would help 👍