Android Crash Reporting: much more crashes reported in Google Play Console than Crashlytics

Question

I have a problem as I have much more crashes reported in Google Play Console than in Firebase Crashlytics. Around 15% in Google Play Console versus 2% in Crashlytics.

Note that most crashes come from C++ code (NDK/JNI).

I don't know which tool gives the correct data.

How to solve this issue?

Thanks.

Answer 1

Have you tried upgrading the NDK version being used in your application? It looks like a problem with Older NDK on newer Google Play Services.

Answer 2

Did you try to filter the crash reports you are getting in the Google Play Console by the app installation source?

It seems that Firebase Crashlytics failed or fails to deliver crash reports for devices where the app was not installed via Google Play, as mentioned in this stackoverflow question or also here. An alternative cause is that the crash appears before Firebase is initialized in the app.

If it turns out that the additional number of crashes comes from non-google-play installations after Firebase already started, and that those exact crashes are not reported in Firebase Crashlytics, you should notify the Firebase team providing screenshots using the Bug Report Form.