Field note
What to export before a crash & stability assessment
Clients who arrive with clean exports finish assessments faster. This checklist covers the minimum set we ask for.
Export crash and ANR summaries for the last 30 to 90 days, depending on how often you ship. Include version codes so we can align spikes with release dates.
Add a one-page note on supported OS versions and the devices you consider in-scope. Without that boundary, low-volume crashes on unsupported phones can distract from issues that matter to your stated audience.
Share release notes for the window under review. Even brief notes help us separate intentional behavior changes from unexpected failures.
Name a technical contact who can clarify symbolication gaps or missing mappings. Assessment time often stalls on incomplete symbols rather than analysis itself.
If privacy rules limit raw logs, ask for aggregated signature tables with counts and sample breadcrumbs. We can work from aggregates when the columns remain consistent across versions.