Recordings and bug reports
A bug report in a minute
One click on the Device card bundles a screenshot, the logs and the device details into a zip, and Share lets someone see the bug live.
Why: a ticket that says “the button doesn’t work” comes back with “which phone, which Android, which build, any logs?”. A bundle answers all of that before anyone asks.
What happens
Section titled “What happens”- Hover the Device card at the bottom of the column next to the screen. It shows the model, the Android version and the build.
- Press Bundle. A few seconds later a zip is downloaded: a screenshot, the logcat collected so far, and the device and app details.
- Attach the zip to the ticket.
- If someone should look at the bug right now, press Share in the session header: a link to this session is copied.
Good to know
Section titled “Good to know”- Logcat is the phone’s system log: what the app and Android wrote while you were testing. Crashes and errors land there, which is why developers always ask for it.
- Full report next to Bundle runs Android’s own
bugreport. It is much bigger and slower; use it only when a developer asks for it. - A session link works only while the session runs, and only for people signed in to the portal. To keep the evidence after you stop, record the session.
If it doesn’t work
Section titled “If it doesn’t work”- Bundle is greyed out or the card says ADB is unavailable: the browser couldn’t connect to the device’s ADB (the Android debugging channel). Wait a few seconds after the device starts; on some portals ADB is turned off.
- Share is greyed out: only the owner of the session (or an admin) can share it.
More details: ADB tools.