Repository navigation
[Android] - Release Application crashes immediately after having upgraded to 0.70.0 with newArchEnabled=true #34684
Description
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
Reacted by Benjamin
Reacted by Luca Bertelli, Pablo Heras, Benjamin and Prateek Chachra
Activity
allemanfredi commentedon Sep 14, 2022
Checking the logs i noted this error:
couldn't find DSO to load: libjscexecutor.soallemanfredi commentedon Sep 15, 2022
I have fixed it by now i get
[-][Android] - Application crashes immediately after having upgraded to 0.70.0 with newArchEnabled=true[/-][+][Android] - Release Application crashes immediately after having upgraded to 0.70.0 with newArchEnabled=true[/+]cortinico commentedon Sep 15, 2022
Can you clarify what have you fixed?
Also, I would need the whole logfile + your
build.gradleto understand what's going on.I've just tested on a blank 0.70 project and I was able to build and run a release app without problems.
allemanfredi commentedon Sep 15, 2022
@cortinico tbh i don't remember i did A LOT of changes. Btw this is the entire log file
And this is my
build.gradlecortinico commentedon Sep 16, 2022
Sorry I can't say from your config where is the problem. Having a smaller reproducer woudl help here.
github-actions commentedon Sep 16, 2022
allemanfredi commentedon Sep 16, 2022
@cortinico It (#34658) seems the same, idk if it can help!
cortinico commentedon Sep 16, 2022
Nope it's not the same as there is reanimated in the stacktrace.
allemanfredi commentedon Sep 16, 2022
i tried to run a different command (
logcatinstead oflogcat | grep io.app) and i get the same.allemanfredi commentedon Sep 16, 2022
@cortinico
This morning i noticed that in the logs there was this:
facebook::jni::throwPendingJniExceptionAsCppException(). For this reason i searched it withinreact-nativefolder and i found this file/node_modules/react-native/ReactAndroid/src/main/jni/react/jni/MethodInvoker.cpp. At that point i added aLOG(FATAL) << methodName_insideMethodCallResult MethodInvoker::invoke(row 226) and i discovered in the logs that the app crashes just after the log and the value ofmethodNameisinstallTurboModulewhich is areact-native-reanimatedfunction.PS: if i run
logcat | grep io.appi don't see my log, instead if i just runlogcati can see it.cortinico commentedon Sep 16, 2022
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 👍
allemanfredi commentedon Sep 17, 2022
Hello @cortinico! This morning i found this error
ReactNativeJS: TypeError: Cannot read property 'localeIdentifier' of null, js engine: hermes. Could be this the cause of the app crash? I'm usingNativeModules.I18nManager.localeIdentifierwithin the my app.I found something similar here.
Edit: If i remove all occurences of
NativeModulesit runs for 1/2 seconds and then crashes but now it appears againSoLoader: couldn't find DSO to load: libjscexecutor.socortinico commentedon Oct 3, 2022
Hey @allemanfredi,
It's a bit hard for us to follow-up to all the issues if the error message keeps on changing.
Have you solved this issue or you're still having problems or not? If so what's the exact error message and the condition that is causing it?
Tohid1999 commentedon Oct 30, 2022
Still have this error after upgrading to react-native 0.70.4
kimvsparrow commentedon Nov 10, 2022
Hi @cortinico I think I've got a reproducer for you:
https://gist.github.com/kimvsparrow/a787cc6936aaa6b8a55eac95ac3d9d7a
If you'd like I can post the whole repo but that seems like too much noise. Let me know if any other information would be helpful!
cortinico commentedon Nov 25, 2022
Thanks for the repro @kimvsparrow
As you:
yarn add realm@11.1.0in your repro, I would suggest you point this issue to Realm instead of React Native.KazakovVS commentedon Dec 14, 2022
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")
Fix Android release version launch crash
asifbadeghar54 commentedon Aug 17, 2023
did any one got solution for this crash.
cortinico commentedon Dec 4, 2023
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