cyberneticlibrary

Diagnose Android crash stack traces

analyze-crashskillsetup L11
jason0404/Jason-Android-Marketplace
What it does

Diagnose Android crash root cause from stack trace

Best for

Quickly pinpointing production Android crashes by separating wrapper exceptions from root cause, mapping to lifecycle, and recommending minimal fixes.

Inputs
  • · Android crash stack trace, ANR snippet, or logcat output
Outputs
  • · Root exception
  • · Crashing lifecycle phase
  • · Most likely trigger
  • · Recommended fixes (Kotlin examples)
  • · Diagnostic logging suggestions
Requires
  • · Project code access (optional)
  • · Android SDK documentation
Preconditions
  • · Stack trace or logcat provided
  • · Sufficient context to identify lifecycle/library
Failure modes
  • · Stack trace truncated or unreadable
  • · Root cause buried under multiple wrapper exceptions
  • · Project code unavailable for hypothesis confirmation
Trust signals
  • · Deepest Caused-by exception preferred over wrapper
  • · Lifecycle timing and framework ownership documented
  • · Confirmed facts separated from hypotheses