Getting SIGABRT Crash on release build. libc.so

Please provide all the information requested. Issues that do not follow this format are likely to stall. ## Description Did looked for related issues did not find any solution for this, the crash is prominent for almost most of the user on my end on my device im unable to reproduce it if someone has faced the crash please help me get away with this. I have hermes enabled for my app. ## React Native version: ``` System: OS: Linux 5.8 Manjaro Linux CPU: (8) x64 Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz Memory: 14.79 GB / 19.40 GB Shell: 5.8 - /bin/zsh Binaries: Node: 12.18.3 - ~/.nvm/versions/node/v12.18.3/bin/node Yarn: Not Found npm: 6.14.6 - ~/.nvm/versions/node/v12.18.3/bin/npm Watchman: Not Found SDKs: Android SDK: Not Found IDEs: Android Studio: Not Found Languages: Java: 11.0.8 - /usr/lib/jvm/default/bin/javac Python: 3.8.5 - /usr/bin/python npmPackages: @react-native-community/cli: ^3.0.5-alpha.1 => 3.2.1 react: 16.13.1 => 16.13.1 react-native: 0.63.2 => 0.63.2 npmGlobalPackages: *react-native*: Not Found ``` ## Steps To Reproduce Unable to produce on my devices but i am able to see this crash on users in production. Probably happening happening while the app starts as i can see in the logs, ## Expected Results This crash is too prominent more than 20% users are facing the crash need a fix ## Snack, code example, screenshot, or link to a repository: ``` Crashed: Thread : SIGABRT 0x000

Posted by afkcodes on Sep 18, 2020, 7:48 PM

Tags

• reliability (SaaS)

Related issues

• Many devs love to shit on the guy from the 'I just want the exe.
• Now imagine how poor people stress if their smartphone bricks or gets damaged or lost.
• Resuming an extended-thinking session fails permanently with 400 "thinking blocks cannot be modified" (transcript stores thinking text as empty but keeps signat
• I'll preface this with a statement that as a European I want European alternatives to succeed, and MS-owned GitHub to shrivel and disappear.
• Yeah, but there’s a world of difference between “not perfect” and “we rounded a few sliders, and now the modal is a nightmare to use”.
• I used to write a lot of native Windows corporate software in the 90's and 2000's and my standard login window was a floating draggable o...