Skip to content

Android ANR Symbolication Using Wrong Debug Image #1859

@Angelodaniel

Description

@Angelodaniel

Android ANR Symbolication Using Wrong Debug Image

Android ANR events are being symbolicated using incorrect debug images, specifically com.google.android.trichromelibrary (WebView-related) instead of the application's own native libraries, even when the ANR occurs in application code unrelated to WebView.

Environment

  • Platform: Native
  • SDK: sentry-native -> sentry-java (Android)
  • Event Type: ANR (Application Not Responding)
  • Application Type: Android app with native code (NDK/C++/Flutter/etc.) and WebView usage

Steps to Reproduce - Not sure if this succeeds 1-1 but I have an example issue internally

  1. Create an Android application that:
    • Uses native code (NDK, C++, Flutter, or similar)
    • Loads a WebView at some point during its lifecycle (which loads com.google.android.trichromelibrary)
  2. Trigger the following sequence:
    • User opens WebView
    • User interacts with WebView content
    • WebView is closed/exited
    • Application continues running
  3. Trigger an ANR in the application's native code (e.g., blocking operation on main thread in game loop)
  4. Upload debug symbols for the application's native libraries to Sentry
  5. Observe the symbolicated stack trace in Sentry

Expected Result

The ANR stack trace should be symbolicated using the application's own debug images (e.g., libflutter.so, libgame.so, etc.), producing human-readable function names, file names, and line numbers that correspond to the application's native code where the ANR actually occurred.

Manual symbolication using the application's debug libraries confirms that proper symbolication is possible and produces the correct results.

Actual Result

Symbolication fails with wrong debug image selection:

  1. Stack frames show symbolicator_status: "missing" or missing_symbol for application code
  2. Frames are incorrectly associated with com.google.android.trichromelibrary package instead of the application's package
  3. Stack trace remains unsymbolicated/partially symbolicated, making root cause analysis impossible
  4. This occurs despite:
    • Both application debug images AND trichromelibrary images being present in debug_meta.images
    • The ANR occurring AFTER WebView was closed, in unrelated application code
    • Manual symbolication working correctly using the same debug images

I'll share customer thread + event link in this case

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels
    No fields configured for issues without a type.

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions