In this guide
A tester writes "it crashed". You need to know what happened, on which phone, and what the system logged. Android can bundle that into a bug report file. Here is how to ask for one without scaring a non-developer.
When to ask for it
Ask for a system bug report when the problem is hard to reproduce, the app closes without a message, or the phone slows down or freezes. For a simple wrong label, a screenshot and two sentences are enough.
Step 1: tester enables developer options
Per Android's documentation, the report is taken from Developer options, so the tester first needs to turn them on. The exact path differs by phone brand and Android version. The usual way is to open Settings, then About phone, and tap the build number seven times. Tell testers to search "Developer options" in Settings if the path differs. Link them to the official page above if they get stuck.
Step 2: reproduce, then take the report
Time matters. The report contains recent system activity, so it should be taken soon after the problem.
- Make the problem happen again (or right after it happened).
- Open Settings, then Developer options, and tap Take bug report.
- Choose the report type offered and tap Report.
- Wait for the notification that the report is ready.
- Tap the notification and share the file.
The documentation describes this flow (Take bug report, choose type, Report, notification, share); labels can vary by device.
Step 3: send it with context
The file alone is not enough. Ask testers to add, in the same message:
- What they did in the app, step by step.
- What they expected and what happened.
- Phone model and Android version.
- App version (from the build or store listing).
- The approximate time it happened.
A copy-paste message you can send:
Thanks for testing. If the app crashes, please do this right away: Settings > Developer options > Take bug report, then share it with me. Add: what you tapped, what you expected, what happened, and your phone model.
Privacy: handle the file with care
A bug report is a system-wide log. It can contain information beyond your app, such as device details and app activity. Tell testers what you receive, ask them to share it only with you, and delete it when you are done. This is general guidance, not legal advice.
Triage
Do not treat every report equally. Group them by crash location and frequency, then fix the ones many testers hit first. See how to prioritize crash reports.
Keep it simple for testers
Many testers will skip a five-step process. Offer two paths: the quick one (screenshot plus description) and the full one (bug report) only for crashes you cannot reproduce. Say clearly which one you need.
More in the Android app testing guide. Related: Choosing an Android test phone and Prepare test data and accounts.
Start here to collect private, structured feedback with device details attached.