SIGABRT crash #47074
Comments
|
|
react-native-bot
added
the
Needs: Repro
|
|
|
We need more information to help you. Try to create a reproducer with this template or update your RN version to latest. |
|
I can't reproduce it because I don't know exactly where it happens. It's a Crashlytics error, and it doesn't occur on my own mobile |
github-actions
bot
added
Needs: Attention
|
Most of the time, I see that there isn't enough memory on those devices |
Nothing on this stacktrace points to React Native hence we're closing this. |
cortinico
added
Resolution: Cannot Reproduce
and removed
Needs: Repro
|
Hm, we're seeing this too, ever since upgrading to RN 0.76 (and 0.76.1). Not new arch. I can't seem to reproduce it in development, but we're seeing tons of events in production too...
Android-only and mostly Android 14 as well. The weird thing is, most of these phones seem to have a decent amount of memory (4GB-8GB). @Nader-CS, do you have a in your app build.gradle by chance? |
|
Also, it looks like this issue happened in older versions of RN as well, but since switching to 0.76 the number of these events has risen exponentially for us (about 30 YTD before 0.76, vs almost 1000 over the last week...). I think the 30 is safe to assume OOM or something, but 1000 over the last week coinciding with this upgrade just does not seem like a coincidence... I’m not ruling out the possibility of it being caused by an upgrade to another dependency that’s causing this either. I’m going to look at how our package.json has changed and report back. |
|
Alright, I was able to get a crash log from Google Play Console with a little bit more info... Looks like this has already been reported in #47352 |
No. |
|
I was getting this error on android 0.76.0 and 0.76.1 when opening the app from a push notification. Downgraded to 0.75.4 in the meantime and the issue went away. |
Same here, it seems to happen when users open the app through a push notification. |
|
This issue should be re-opened..same problem: terminating due to uncaught exception of type facebook::jni::JniException: com.facebook.react.common.JavascriptException: EarlyJsError: TurboModuleRegistry.getEnforcing(...): 'PlatformConstants' could not be found. Verify that a module by this name is registered in the native binary. Happens after upgrade to 0.76.1 in production without the ability to reproduce |
|
The crash happens when the users open a firebase notification when the app is not in the background or foreground, i.e killed. |
|
@nes123 we have the exact same thing with 0.76.5 (old architecture). Were you able to overcome this issue? CC: @cortinico |
Yes, once i upgraded, and updated all the firebase packages (not sure if it made a difference), we dont have this crash any more. |
|
@nes123 thx for the quick reply! We're using latest firebase - 21.6.1, is there anything else you upgraded that might help? |
|
@gituser8796 no, just that. |
Description
when app opened , it crashed at runtime due to SIGABRT error , it happens mostly android 14 and and mostly in samsung devices
Steps to reproduce
React Native Version
0.73.7
Affected Platforms
Runtime - Android
Output of
npx react-native infoStacktrace or Logs
Reproducer
i don't know where exactly the issue , but it not happened in ios
Screenshots and Videos
The text was updated successfully, but these errors were encountered: