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
[firebase-crashlytics] Fatal errors aren't sent to Firebase console #234
Comments
Same problem. It works with iOS, doesn't with Android. |
@nicolapiccoli I didn't really find a solution, but I think it is because my app was running in debug mode at this time. When the app was finally pushed to the play store, crashes were properly sent. You can try building the app in release with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
On Android, crashing the application with firebase().crashlytics().crash() at launch or on tap of a button doesn't seem to create a report and send it to the Firebase console.
However, non-fatal errors registered using
recordError()
are logged. Only fatal errors alone are not.I tried using an emulator as well as a real device.
I didn't encounter this problem on iOS.
I used
adb -d shell setprop log.tag.FirebaseCrashlytics DEBUG
in order to debug with Android Studio Logcat window.LOGCAT
When launching the app:
Then, I immediatly click on the crash test button:
This follows right after the RuntimeException occured and the error screen on in the app is still visible:
When I restart the app:
I noticed the user ID is missing when I restart the app. I don't know if it matters in this situation.
My app configuration (in app.ts):
The text was updated successfully, but these errors were encountered: