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
{{ message }}
Repository navigation
Commit 56d97d5
Browse filesBrowse the repository at this point in the historyBrowse files
fix(android): Remove AndroidRuntimeManager to prevent ANRs during SDK init (#5127)
* fix(android): Remove AndroidRuntimeManager to prevent ANRs during SDK init
StrictMode.setVmPolicy()/setThreadPolicy() calls inside
runWithRelaxedPolicy() triggered binder IPC on the main thread, causing
ANRs (SDK-CRASHES-JAVA-32FQ 34k+, SDK-CRASHES-JAVA-32PH 21k+,
SDK-CRASHES-JAVA-32Q9 18k+ events). StrictMode only logs warnings in
production by default, so relaxing it is unnecessary and harmful.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* changelog: Add entry for AndroidRuntimeManager removal
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix(test): Remove initNotThrowStrictMode test
This test validated that StrictMode with penaltyDeath() didn't crash
during SDK init. Since we removed the RuntimeManager that relaxed
StrictMode, this test is no longer applicable — the SDK no longer
attempts to suppress StrictMode violations.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
0 commit comments