-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[android] app crash -> JNI DETECTED ERROR IN APPLICATION: java_object == null #2710
Comments
Issue validatorThe issue is valid! |
Issue seems to be caused by wrapping my app with |
@piaskowyk any idea? |
Give me some time, I will try to reproduce your issue on your repo. I will notify you about the progress. |
I can trick out the problem. Additional Info: |
Facing the same issue using on Expo SDK 43
|
Also caused by SafeAreaProvider? |
Yes, because of SafeAreaProvider |
App is also crashing on real android device:
|
Same issue in react-native debug build version 0.67.2 |
same here, I get the error also in the simulator |
Still a thing here also :/ {
"dependencies": {
"expo": "^44.0.6",
"expo-dev-client": "^0.8.4",
"react": "17.0.1",
"react-dom": "17.0.1",
"react-native": "0.64.3",
"react-native-reanimated": "^2.3.1",
"react-native-gesture-handler": "^2.1.0",
"react-native-safe-area-context": "^3.3.2",
}
} Attached Stacktraces (4)
|
Also seeing a crash here on a debug build Reanimated 2.4.0 and RN 0.66.4
Flipper also gave this, not sure if helpful:
|
I encountered this error due to a NaN value as the "top" value in an absolutely positioned view. Giving it an appropriate value fixed this issue. |
After upgrading to Expo SDK 45, I also encounter the same crash. |
I think that bug may be fixed by expo/expo#17282. |
The PR did not fix the issue unfortunately |
This issue has been fixed in Expo SDK 45.0.3 and expo-dev-client 0.9.5. Thanks @lukmccall |
same for me, seems that SafeAreaProvider cause this crash for me. |
We are seeing this crash when calling restart in the app programmatically. We need to do a restart to support RTL, but Android phones are occasionally crashing in production due to this. We are not using Expo, is there anything we can do besides removing safe area context? |
We're seeing this crash as well. It's being triggered because of codepush reloading the JS. |
Hi there, I'm encountering the same issue. Did anyone found a solution about that ? |
Hi Team, Did anyone found a solution for this ? |
Hi, I had the same issue.
please tell me if anyone has resolved the issue. Thanks |
Any updates here? We're encountering the same issue across two different versions of react native. Crashes on hermes too, when receiving codepush updates (ostensibly bc of restarts) on both runtimes. Of course on hermes you can't really see the actual problem via stacktrace though |
I'm experiencing the same issue with:
@mwegener-com, could you share how did you manage to do that trick of yours that you mention in #2710 (comment) ? @tomekzaw, would the fix from #3954 help in the case of this issue? |
@mwegener-com @tomekzaw @sebbalex @vonovak did you get any solution for this as my log is Unknown java_vm_ext.cc:579] JNI DETECTED ERROR IN APPLICATION: JNI ERROR (app bug): jobject is an invalid JNI transition frame reference or invalid reference: 0xb4000077907cf908 (use of invalid jobject) let me know if you guys got this kind of crash |
We are facing the same issue with the listed modules, need the same information |
In my case,
I had to uninstall my app in my emulator and I also added this line in
and finally ran |
I can confirm that the solution proposed above solves the problem. |
Description
My android crashes on startup. Do you have any idea?
Same problem on Android 29 and 30
Same problem with Hermes enabled
Using expo-dev-client.
Expected behavior
app working fine.
Actual behavior & steps to reproduce
Sometimes I also get this error:
or this:
Package versions
Affected platforms
Probably import aspect in log:
The text was updated successfully, but these errors were encountered: