Skip to content

[Bug]: Getting too much ANR 100% in background state. #2628

Closed

Description

@govindj6

What happened?

[OneSignal-ANR-Watchdog] OtelAnrDetector: ⚠️ ANR detected! Main thread unresponsive for 7880ms

Steps to reproduce?

Not able to reproduce.

What did you expect to happen?

It should not create ANR in the background state

OneSignal Android SDK version

5.7.1

Android version

12

Specific Android models

78% in android version 12.
18% in android version 11.
4% in android version 13.

Relevant log output

Code of Conduct

  • I agree to follow this project's Code of Conduct

Activity

  1. abdulraqeeb33 commented on Apr 29, 2026

    @abdulraqeeb33
    Contributor

    Hi @govindj6 , we just released several fixes for ANRs in the background - behind a feature flag.
    Could you please update to this version https://github.com/OneSignal/OneSignal-Android-SDK/releases/tag/5.8.0 and also share your appId. I can enable the feature flag and perhaps you could help us out with your findings.

  2. self-assigned this
    on May 1, 2026
  3. nan-li commented on Jun 3, 2026

    @nan-li
    Contributor

    Closing due to no response. Also, for additional context, the log statement "⚠️ ANR detected! Main thread unresponsive for..." captures all potential ANR cases affecting an app, not just those caused by OneSignal.

    This may be followed up with either:

    1. "ANR is not OneSignal-related, skipping report"
    2. "OneSignal-related ANR detected, reporting..."
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions