From 673b7513f104911ec3119927579eef16fb376d15 Mon Sep 17 00:00:00 2001 From: Rosa Trieu Date: Mon, 15 Jun 2026 13:32:46 -0700 Subject: [PATCH] [DOCS-14668] Add clarifying note about ANRException in Android ANR reporting Co-Authored-By: Claude Sonnet 4.6 --- content/en/error_tracking/frontend/mobile/android.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/en/error_tracking/frontend/mobile/android.md b/content/en/error_tracking/frontend/mobile/android.md index 6e61611fdc6..d649f6d05e5 100644 --- a/content/en/error_tracking/frontend/mobile/android.md +++ b/content/en/error_tracking/frontend/mobile/android.md @@ -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.