Skip to main content
Version: 2.1.x

Android ANR Exit Detection

Automatic Detection: This feature is automatically activated for both debug and release builds on Android 11+ (API Level 30+).

Type: 27 | Severity: Fatal

Appxiom SDK automatically tracks historical process terminations caused by ANR (Application Not Responding) events using Android 11+ ApplicationExitInfo system APIs.

When an application process is killed by the OS due to a main thread freeze or unresponsive UI state, Appxiom captures the exit record upon the next app startup and reports an issue of Type 27 (ANR_EXIT_ISSUE) to the dashboard.

Overview​

Unlike live ANR detection (Type 25) which monitors the UI thread in real-time, ANR Exit tracking captures OS-enforced process kills reported by the operating system after process termination.

Key Capabilities​

  • OS-Level Precision: Retrieves exact OS termination reasons and process diagnostic traces.
  • Post-Mortem Analysis: Captures exit data even if the process was abruptly killed by the system.
  • Zero Overhead: Processes exit records asynchronously on app launch.

Integration Requirements​

This feature works automatically once you complete the basic SDK integration. No additional code or configuration is required.

// No additional code needed - automatic detection on API Level 30+
// Just ensure basic Appxiom SDK integration is complete

Frequently Asked Questions​

Q: What is the difference between ANR Issue (Type 25) and ANR Exit Issue (Type 27)?​

A.

  • ANR Issue (Type 25): Detected in real-time while the application is actively running and the main thread is blocked.
  • ANR Exit Issue (Type 27): Captured post-mortem on the subsequent app launch using OS ApplicationExitInfo logs when the OS terminated the app process due to an ANR.