react-native: libc.so Crash report by firebase crashlytics in android app

I have got rid of this issue by enabling Hermes

I also have the same issue, 200 crashes and 75% due to Samsung devices such as:

• Galaxy A51
• Galaxy S10+
• Galaxy S10e
• Galaxy S10
• Galaxy S21 FE 5G
• Galaxy Note10+
• Galaxy S20+
• Galaxy Note10 Lite
• Galaxy S20 Ultra 5G
• Galaxy Z Flip3 5G
• Galaxy A13
• …

Had same problem. Hermes was always enabled so that wasn’t the issue. It was the WebView, found some solutions here https://github.com/react-native-webview/react-native-webview/issues/1915

opacity=0.99 in WebView and overScrollMode ="never" in ScrollView fixed the issue. Not a single crash since

Just a small heads up: without a reproducer this can’t be fixed. Moreover, some of the posted stacktraces have references only of libc and libhwui, which are outside of our control, so I’m unsure this is even related to React Native in the first place.

Similar issues on RN 0.67.3 228 crash events affecting 219 users in the last 24 hours. 86% Samsung.

Crashed: Thread :  SIGSEGV  0x0000000000000048
#00 pc 0x6703bc libjsc.so 
#01 pc 0x624 linux-vdso.so.1 
#02 pc 0x16524 libutils.so 
#03 pc 0x16408 libutils.so 
#04 pc 0x151dcc libandroid_runtime.so 

I am also having the issue. Any update, please?

I have the save issue (react-native: 0.67.1) only on Android 12: Galaxy S20 FE 5G Galaxy S21 5G Galaxy S21 Ultra 5G …

I can confirm that I too got the same crash report. Further investigating, I found that this could be a recurring issue on Samsung devices [1][2][3].

Here’s a similar thread on this issue.

Furthermore, in my case, this issue was seen on A12 Samsung devices when the app was launched with wifi on, and then it crashed when the wifi was turned off. I found a thread on this exact issue here

Can everyone make sure they have sufficient memory before the crash? I have this same exact crash but at the time of it, free RAM is around 20-200 Mb only so I think that also might be a reason for it.

In crashlytics most report 40mb to 150mb free RAM.

I also met this issues. Is there any solution for this?

Add compileOptions with JavaVersion 1.8 like this under your app level build.gradle android block:

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

This fixed my issue in RN 0.71

We’re also facing the same issue with Samsung immediately after the first screen in the app gets mounted Device: Galaxy A52 5G

Same issue for me, RN 0.66 Devices are more diverse, data coming from around 70 devices:

In our case we were having this same crash on Android with error log: libc: Fatal signal 11 (SIGSEGV) ... We don’t have hermes enabled.

We found out that this was due to a compatibility issues of two dependencies: react-native-reanimated v2 + realm as stated in this thread: https://github.com/realm/realm-js/issues/3837 Realm doesn’t have yet support for hermes, they are currently working on it.

We have decided to remove realm from the project and we are not experiencing this crash anymore.

Is there any way to reproduce this issue in development mode? This issue only exists in production mode.

same issue 😕 any update?