Skip to content

User sessions

Analyze → User Sessions shows every app session.

At the top, highlight cards show Live sessions, Pending sessions (sleeping) and Sessions with problems, refreshed every 30 seconds.

Filter by status — All, Live, Sleeping, Ended — or with the filter bar. Each row shows the user (or Not logged in), status with crash / network-error / trace-error counts, device, events, duration (counting live for active sessions), version and start time.

Indicator Meaning
Green dot Live session
Warning 1–5 errors
Problematic More than 5 errors

Click a session to open it. The header shows the user, status, a Rooted badge if applicable, the session UID and summary chips.

  • Session — user, location, app, version, duration, event count, start/end.
  • Device — model, brand, OS, device UID, rooted, status, and Block Device / Unblock Device.
  • Event Breakdown — counts per type (Screen, Network, Click, Crash, Trace, Lifecycle); expand a tile to list events.

Every event of the session in order, with the time since session start (+1.2s) and gap markers. Filter by Lifecycle, Screens, Network, Clicks, Crashes or Traces. Lifecycle events read App Launched, Returned to Foreground, Went to Background, App Closed. Click an event for full details — headers and bodies for requests, stack traces for crashes.

The Session Trail: device-audit events with a location, colored by security state (Clean, Rooted, Simulator, Corrupted). Requires Device Audit to be on and the app to hold a location permission.

All crashes, network errors (status ≥ 400) and error-level traces in the session, with severity.

Inspect and change the app’s SharedPreferences on the device — for debugging a user’s state. Only available while the session is not ended.

  • Capture — fetch a snapshot of all preference files (arrives within ~30 s).
  • Expand a file to see its keys. Use the pencil to edit a value.
  • Select keys and Clear Selected, or Clear this file / Clear All.
  • Command History shows each command’s status: pending, received, executed, failed, expired.

Sending commands requires logs:manage.

Click Generate Summary for a plain-language narrative of what the user did and what went wrong. Verify it against the timeline.