Skip to content
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

[BUG]: Investigate why Crashlytics has no issues #5352

Open
BenHenning opened this issue Mar 5, 2024 · 0 comments
Open

[BUG]: Investigate why Crashlytics has no issues #5352

BenHenning opened this issue Mar 5, 2024 · 0 comments
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.

Comments

@BenHenning
Copy link
Sponsor Member

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:

  • Identify what causes issues to appear.
  • Verify that the app is logging the correct data for these situations (via local debug verification).
  • Investigate where the failure is actually happening.

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).

@BenHenning BenHenning added bug End user-perceivable behaviors which are not desirable. triage needed labels Mar 5, 2024
@adhiamboperes adhiamboperes added Impact: High High perceived user impact (breaks a critical feature or blocks a release). Work: High It's not clear what the solution is. and removed triage needed labels Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Development

No branches or pull requests

2 participants