Session History
The Session History page provides a complete record of all simulator sessions run within your organization. Use it to review past activity, debug issues, and track device usage over time.
Overview
Every time a user in your organization starts a simulator session (iOS, Android, or Roku), VibeView records it. The Session History page lists these sessions in reverse chronological order, showing key metadata at a glance: which device was used, how long it ran, and whether it completed successfully.
Session Details
Each session entry displays the following fields:
| Field | Description |
|---|---|
| Session ID | A unique identifier for the session, useful for support requests and API references. |
| User | The email of the team member who started the session. |
| Device | The name of the simulator or emulator that was used (e.g., “iPhone 15 Pro”, “Pixel 7”), with its category (phone, tablet, or TV) shown underneath. This is a snapshot captured at session start, so it remains accurate even if the device is later renamed or removed. Platforms include iOS, Android, and Roku. |
| OS Version | The operating system version running on the device at the time of the session (e.g., “17.2”, “14.0”). Also captured as a snapshot at session start. |
| Status | The current lifecycle state of the session (see below). |
| Duration | The total time the session ran, rounded to whole minutes. Still-running sessions show a live, ticking duration marked “(live)”. |
| Date | When the session started. |
Session Statuses
A session moves through the following statuses during its lifecycle:
| Status | Meaning |
|---|---|
| Pending | The session has been requested but the device has not yet been allocated. |
| Starting | A device has been allocated and the simulator is booting up. |
| Active | The session is live and streaming. |
| Stopping | The session is in the process of shutting down. |
| Stopped | The session ended normally. |
| Failed | The session encountered an error and could not start or continue. |
Filtering and Search
The Session History page provides several ways to narrow down the list:
- Filter by status — Pick a status (All, Active, Stopped, or Failed) to show only sessions in that state. For example, filter to “Failed” to investigate problematic sessions.
- Filter by device type — Restrict results to iOS-only or Android-only sessions.
- Search — Enter a full or partial session ID or user email to locate specific sessions.
Filters can be combined. For example, you can list all failed Android sessions started by a specific user.
Duration Tracking
Session duration is automatically calculated from the difference between start time and end time. For active sessions, the duration updates in real time.
Duration tracking is useful for:
- Usage monitoring — Understand how long team members spend in simulator sessions.
- Cost estimation — Track cumulative device usage across the organization.
- Debugging — Identify sessions that ended unexpectedly quickly or ran unusually long.
Related: Test run history
Automated test runs have their own history and detail views under the Tests section. The test run detail page shows per-step results, a visual regression banner, and the build that was under test. Navigate there from a suite page or the tests dashboard.
Tips
- Sessions are scoped to your organization. You will only see sessions started by members of your org.
- The device name and OS version shown are snapshots taken when the session started. If a device is updated or removed after the session, the historical record remains intact.
- Use the session ID when contacting support or referencing sessions in API calls.