[markushi]

📜 Description

On Android 17 (API 37) and above, AppLifecycleIntegration now subscribes to ActivityManager.registerAnrWarningListener. These usually fire halfway (e.g. input dispatch at 2.5s of the 5s limit, forground service starts at 5s of the 10s limit)

Each warning becomes an app.anr breadcrumb (type: system, level: warning, message: ANR warning) with this data:

• anr_type: the AnrTypes constant as a readable name (for example input_dispatch, broadcast_of_intent, start_foreground_service). An unknown value is kept as unknown (<n>).
• anr_id, timeout_ms, consumed_ms
• description: the description from the system. It is not set if the system gives an empty value.

Details:

• The listener is registered only when enableAppLifecycleBreadcrumbs is enabled.
• Registration is a binder call, so it runs on the SDK executor service, not on the thread that calls Sentry.init.
• The callback runs on the binder thread that delivers it. As breadcrumb creation is cheap, this should be fine.
• close() unregisters the listener. If the executor drops or rejects the unregister task, it runs inline. A register task that is still in the queue after close() does not register the listener.
• AppLifecycleIntegration now takes (Context, BuildInfoProvider) in its constructor. The public no-arg constructor is kept as @Deprecated. With it, the ANR warning listener is not installed.

💡 Motivation and Context

The ANR warning arrives before the ANR. If the app then crashes, records an error, or is killed for the ANR, the event breadcrumbs show that the main thread was already slow, and they show which ANR type and how much of the timeout was used.

• resolves: Add support for reporting AnrWarnings #6244
• resolves: JAVA-771

💚 How did you test it?

• Added tests

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 Next steps

• Docs: add the app.anr breadcrumb to the Android breadcrumbs page.

🤖 Generated with Claude Code

[linear-code]

JAVA-771

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against 6c235cd

[sentry]

📲 Install Builds

Android

🔗 App Name	App ID	Version	Configuration
SDK Size	io.sentry.tests.size	8.63.0 (1)	release

⚙️ sentry-android Build Distribution Settings

[cursor]

Cursor Bugbot has reviewed your changes and found 3 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 6c235cd. Configure here.}

[cursor]

Lock held across binder registration

Medium Severity

activityManager.registerAnrWarningListener is a binder IPC call, but it runs while lock is held, and the failure path also logs under that lock. close() acquires the same lock and often runs on the main thread, so a slow or stuck ActivityManager call can block Sentry.close() and show up as an ANR. Unregister already performs its binder call after releasing the lock.

 

^{Triggered by project rule: PR Review Guidelines for Cursor Bugbot}

^{Reviewed by Cursor Bugbot for commit 6c235cd. Configure here.}

[cursor]

Broad catch missing required handling

Medium Severity

The new RuntimeException catches around the ActivityManager binder calls sit at a system-service boundary but do not call ExceptionUtils.rethrowIfFatal first and have no comment explaining why the catch is broad or what happens on failure (listener not installed, or leftover registration). Nearby API 37 code such as MemoryLimiterIntegration follows that pattern.

Additional Locations (1)

• sentry-android-core/src/main/java/io/sentry/android/core/AppLifecycleIntegration.java#L251-L256

 

^{Triggered by project rule: PR Review Guidelines for Cursor Bugbot}

^{Reviewed by Cursor Bugbot for commit 6c235cd. Configure here.}

[cursor]

Null application context skips ANR listener

Low Severity

The new constructor stores context.getApplicationContext() directly. That method can return null for some Context implementations (ContextImpl is called out in ContextUtils). scheduleRegisterAnrWarningListener then treats a null context as “no Context” and never installs the ANR warning listener. Other integrations, including MemoryLimiterIntegration and AnrV2Integration, use ContextUtils.getApplicationContext, which falls back to the original context.

 

^{Reviewed by Cursor Bugbot for commit 6c235cd. Configure here.}