Open hyvong-iclic opened 10 months ago
Same problem. It works with iOS, doesn't with Android. @hyvong-iclic Did you find any reason/solution to this?
@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 ns run android --release
and check if that works for you too.
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):