-
Notifications
You must be signed in to change notification settings - Fork 647
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
Crashed: Thread : SIGABRT 0x0000000000000000 from Crashlytics #818
Comments
Hi. Would you be able to provide a repro for this? |
@jpporto Right now I am unable to provide a repo to reproduce it because of the issue we face on the commercial app. We catch the issue from the Crashlytics log. Just information, by the time the issue happens, our end-user turns off the internet connection, and the app saved every failed network request to redux-persists using AsyncStorage (@react-native-async-storage/async-storage). Do you think any relevance to saving a lot of text to AsyncStorage causes a problem with Hermes? |
There is nothing we can do without a proper repro I am afraid. |
also facing the same issue
|
having the same issue
|
Did you find any fix for them? |
Unfortunately, we can't provide much help here without a repro or symbolicated stack trace. Please feel free to reopen this if you're able to provide a minimal repro. |
Bug Description
We observe crashes on Firebase Crashlytics have relevant log to Hermes.
Hermes version: 0.11
React Native version (if any): 0.68.2
OS version (if any): Android 12
Device: Galaxy Tab S7 FE
Platform (most likely one of arm64-v8a, armeabi-v7a, x86, x86_64):
Steps To Reproduce
Crashlytics log:
The Expected Behavior
The text was updated successfully, but these errors were encountered: