A crash is the most useful thing you can find, if you can tell the developer what led to it. Stay calm and work through this list.
Right after the crash
- Do not close everything at once. Look at the screen: is there an error message? Write down its exact text or take a screenshot.
- Note what you just did. The last two or three actions matter most.
- Note the screen you were on and what was on it (a form, a list, a video).
Retry once or twice
Reopen the app and repeat the same steps.
- Crashes again: you have a reproducible bug. Write down the exact steps.
- Does not crash again: say so. "Crashed once, could not repeat in two tries" is still useful.
- Crashes at start: note that, and whether a restart of the phone or computer changes anything.
Do not try more than a few times. The goal is the pattern, not a marathon.
What to report
- Steps from a fresh start to the crash
- What you expected and what happened (closed, froze, blank screen)
- How often: every time, sometimes, once
- Device, OS version, app version
- Conditions: network on or off, low storage or battery, a permission just granted or denied, rotation, switching apps
- Screenshot of any message
What not to do
- Do not guess the cause. "I think it is the database" helps less than the steps.
- Do not post the crash anywhere public. Send it to the developer as private feedback.
- Do not include personal data from the screen. See Screenshot tips for testers.
Example
Example report:
Crash on 'Save'. Steps: fresh start, open Notes, create note with a photo, tap Save. App closes. Happened 3 of 3 times; without the photo it saves fine. Device and OS noted below. Expected: note is saved.
Testers test the app as published in the store, so the developer will want the app version too.
Back to Become an app beta tester. Related: Common beta tester mistakes, Beta tester vs QA tester.