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.

Sign up for GitHub

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

Jump to bottom

Investigate Null Crashes in the App #10172

Open
2 tasks
timwright12 opened this issue Nov 13, 2024 · 0 comments
Open
2 tasks

Investigate Null Crashes in the App #10172

timwright12 opened this issue Nov 13, 2024 · 0 comments
Labels
front-end Ticket requires front-end work global Issues for the global team

Comments

@timwright12
Copy link
Contributor

Description

On November 9, 2024 in v2.40.0 of the app for iOS we saw a small spike in crashes (only 7), then a few others trailing off as days passed by. This spike by itself isn't a concern, but we still want to look into places in the app that are crashing because of null instances. Ideally we want to throw an informative error instead of crashing.

Breadcrumbs in the crash report will show the actions of the user leading up to the crash.

Helpful Links

Acceptance Criteria

  • Identify areas of the app related to the crash report that could crash with a null response
  • Create follow up tickets to defensively code against these null responses and error instead of crashing
@timwright12 timwright12 added front-end Ticket requires front-end work global Issues for the global team labels Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
front-end Ticket requires front-end work global Issues for the global team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@timwright12