[BUG]: Investigate why Crashlytics has no issues #5352
Labels
bug
End user-perceivable behaviors which are not desirable.
Impact: High
High perceived user impact (breaks a critical feature or blocks a release).
Work: High
It's not clear what the solution is.
Describe the bug
The current production Crashlytics dashboard in Firebase is showing zero issues despite having a steady stream of crashes being tracked.
Steps To Reproduce
Open up the Crashlytics view in the Firebase console for oppia-android-dev and observe there are crashes (sometimes; you may need to initiate a crash for it to show up since not many devs have analytics enabled) but no issues.
Expected Behavior
Issues should show up in Crashlytics.
Ideally, the work here is to:
Screenshots/Videos
No response
What device/emulator are you using?
No response
Which Android version is your device/emulator running?
No response
Which version of the Oppia Android app are you using?
No response
Additional Context
Firebase analytics will need to be enabled in local developer versions of the app to investigate this issue. Also, the assignee must have access to the developer Firebase project (contact @BenHenning or @adhiamboperes).
The text was updated successfully, but these errors were encountered: