You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've gotten reports that customers with popular mobile applications can receive, in some cases, 1000s of ANR issues a day. With this volume of ANR issues, it's difficult to sort out signal from noise.
Potential Solution
A thought on my mind, if we included ANR information in Mobile Screens, with additional contextual information surrounding the ANR, e.g., an ANR error happens most frequently when interacting with widget X (getsentry/sentry-dart#2251), could we provide enough context surrounding these issues that they're easier to manage and debug.
Additional Notes
Once we have this additional context, we should cross link ANR issues and insights.
The text was updated successfully, but these errors were encountered:
Problem
I've gotten reports that customers with popular mobile applications can receive, in some cases, 1000s of ANR issues a day. With this volume of ANR issues, it's difficult to sort out signal from noise.
Potential Solution
A thought on my mind, if we included ANR information in Mobile Screens, with additional contextual information surrounding the ANR, e.g., an ANR error happens most frequently when interacting with widget X (getsentry/sentry-dart#2251), could we provide enough context surrounding these issues that they're easier to manage and debug.
Additional Notes
Once we have this additional context, we should cross link ANR issues and insights.
The text was updated successfully, but these errors were encountered: