Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Enrich instrumentation data for App Terminations with ANR and CRASH_NATIVE reasons #90

Open
murki opened this issue Oct 29, 2024 · 0 comments · May be fixed by #95
Open

Enrich instrumentation data for App Terminations with ANR and CRASH_NATIVE reasons #90

murki opened this issue Oct 29, 2024 · 0 comments · May be fixed by #95
Labels
android

Comments

@murki
Copy link
Contributor

murki commented Oct 29, 2024 •
edited
Loading

Currently we use activityManager.getHistoricalProcessExitReasons() to obtain the previous session's ApplicationExitInfo and log an "App Termination" event that would be associated with such session.

According to their documentation ApplicationExitInfo.getTraceInputStream() returns extra information in the form of traces for REASON_ANR or REASON_CRASH_NATIVE (starting with API level 31). We should extract this information when available and attach it as one of the metadata fields sent in the event. See: https://developer.android.com/ndk/guides/debug

Most of the current logic lives in this class

capture-sdk/platform/jvm/capture/src/main/kotlin/io/bitdrift/capture/events/lifecycle/AppExitLogger.kt

Line 153 in f99fb64

// TODO(murki): Extract getTraceInputStream() for REASON_ANR or REASON_CRASH_NATIVE

@murki murki added the android label Oct 29, 2024
@murki murki changed the title Enrich instrumentation for App Terminations with ANR and CRASH_NATIVE info Enrich instrumentation data for App Terminations with ANR and CRASH_NATIVE reasons Oct 29, 2024
@jaredsburrows jaredsburrows linked a pull request Nov 4, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
android
Projects
None yet
Milestone
No milestone
1 participant
@murki