Crash Log Analysis
Automatically parse crash logs from your crash reporting group, deduplicate by stack trace fingerprint, score by frequency and severity, and generate an analysis report with message links.
How to Use
Analyze crash logs in the "Crash Log" group and generate a briefing to send back
Workflow
- Locate the crash log group
- Search recent crash messages using multiple keyword groups (crash, ANR, OOM, exception, etc.)
- Deduplicate by stack trace fingerprint and merge similar crashes
- Score by frequency and severity (HIGH / MEDIUM / LOW)
- Output an analysis report with message links
- The report can be sent back to the group
Severity Levels
| Level | Description |
|---|---|
| 🔴 HIGH | High frequency (≥3/day) or startup crash, needs immediate fix |
| 🟡 MEDIUM | Moderate frequency (1-2/day), impacts user experience |
| 🟢 LOW | Low frequency or already patched, can be deprioritized |
Example Output
# Crash Log Analysis Report — 2026-06-04
## 🔴 HIGH — NullPointerException in ChatAdapter (12 times)
- Stack: ChatAdapter.bindViewHolder:156 → MessageItem.bind:89
- Most recent: Today 14:32
- Affected versions: 3.2.1, 3.2.2
- [View original message](https://typex.im/chat/xxx/msg/yyy)
## 🟡 MEDIUM — SQLiteDiskIO (3 times)
- Stack: DatabaseHelper.onUpgrade → SQLiteDiskIO
- Most recent: Today 09:15
- Affected versions: 3.2.2
- [View original message](https://typex.im/chat/xxx/msg/zzz)
## 🟢 LOW — NetworkTimeout (1 time)
- Single occurrence, likely a network fluctuation
Tips
- Analyze by time range: "Analyze crashes from this week"
- Filter by version: "Only check crashes from version 3.2.1"
- Use message links to reference the original logs precisely