Skip to content

[DOCS-14668] Add clarifying note about ANRException in Android ANR reporting #37525

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

Open
rtrieu wants to merge 1 commit into
base: master
Choose a base branch
from
+2 −0
Open

[DOCS-14668] Add clarifying note about ANRException in Android ANR reporting #37525

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions content/en/error_tracking/frontend/mobile/android.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -482,6 +482,8 @@ Rum.enable(rumConfig);

ANRs are only reported through the SDK (not through Logs).

**Note**: If you see `com.datadog.android.rum.internal.anr.ANRException` in your crash reports, the Datadog SDK did not cause the ANR. `ANRException` is the SDK's mechanism for detecting and surfacing ANRs in Error Tracking. The root cause is always application code blocking the main thread.

#### Reporting fatal ANRs
Fatal ANRs result in crashes. The application reports them when it's unresponsive, leading to the Android OS displaying a popup dialog to the user, who chooses to force quit the app through the popup.

Expand Down
Loading