The Session history page lists every device session in your organization: where it came from, which app it ran, who started it, on which device, and how it ended. Open it from Session history in the sidebar. It covers every platform: iPhone and iPad, Apple TV, Android phones and tablets, Android TV and Roku.
The list
Sessions are listed newest first.
| Column | What it shows |
|---|---|
| Source | Where the session came from. See Where a session came from. |
| App | The app the session started with: its icon, its name and the build version, for example “1.2.0 (45)”. A session started on a bare device shows a dash. An app installed later in the session is not shown here. |
| Who | The team member who started it, the name of the API token that started it, or Visitor for someone who opened a share link or an embed. |
| Device | The device model and its OS version on one line, for example “iPhone 16 Pro · iOS 18.0” or “Chromecast · Android TV 14 (API 34)”, with phone, tablet or TV underneath. The device is recorded when the session gets it, so the row stays accurate even if the device is later renamed or removed. |
| Status | The session’s current state (see below). Under it, why the session ended, in words: for example “Idle timeout”, “Stopped by the user” or “Session length limit”. For a failed session, why it failed. |
| Duration | How long the session ran, rounded to whole minutes. A session that is still running ends in ”, live”. A session still waiting for a device shows ”-”, and one under a minute shows <1 min. |
| Started | When the session got its device. For a session still waiting for one, when it was requested. |
Where a session came from
| Source | Meaning |
|---|---|
| Dashboard | Someone on your team started it: from the dashboard, or with the API, the SDK or the CLI (other than vibeview dev). |
| Agent | A coding agent drove the device, or holds it. |
| CLI dev | vibeview dev started it, to run your React Native app with live reload. |
| Test run | It was started to run a test or a group, from the dashboard, a schedule or another session. |
| CI | A CI command or an API test run started it, with an API token. |
| Share link “name” | Someone opened it from an app share link. An unnamed link is shown as the app’s name followed by “link”. |
| Embed “name” | Someone opened it in an embed on your own site. |
Share-link and embed sessions are counted against the person who created the link or embed, but Who shows Visitor, because the person watching is not on your team. In the downloaded file, the email shown on those rows is the owner of the link or embed, not the visitor.
Filtering and search
- Quick filters above the list:
- All;
- You and your agents: sessions your team, its agents and
vibeview devstarted; - Visitors: share links and embeds;
- Tests and CI.
- App shows the sessions of one app.
- Status offers Active, Starting, Stopping, Stopped and Failed. Starting includes sessions still waiting for a device.
- Devices offers iOS, Apple TV, Android, Android TV and Roku.
- Time offers the last hour, 24 hours, 7 days (the default), 30 days or All time.
- Search: type a full or partial session ID, or an email, in the search box at the top of the page. The list updates when you stop typing.
Filters combine. For example, you can list every failed Apple TV session of one app in the last 24 hours. When nothing matches, the page says so and offers Clear filters. With no filters but the default 7-day window, an empty list says there were no sessions in the last 7 days and offers Show the last 30 days.
The list shows 100 sessions at a time. Load more at the bottom shows the next 100.
Session details
Click a session to open its details:
- Session ID: the full ID, with a copy button. Use it when you contact support or call the API.
- App: the app and build the session started with, and an Open app link to the app’s page.
- Source:
- for a share link or an embed, an Open in Sharing link that opens it on the Sharing page;
- for a test run or a CI run, an Open the run link;
- a share link or embed that has since been deleted is marked “(deleted)”.
- Who and Device: as in the list.
- Timeline: what happened, in order. Only the steps the session recorded are shown:
- Waiting for a device, while it is still queued;
- Device assigned;
- Device ready;
- App opened, for a test run;
- App installed, for an app installed after the device came up;
- An agent first drove it;
- Ended, with the reason.
- Duration, and Minutes once the session has ended: how long it ran.
Session statuses
| Status | Meaning |
|---|---|
| Pending | The session has been requested but the device has not yet been allocated. |
| Starting | A device has been allocated and 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. |
Export CSV
Export CSV at the top of the page downloads the sessions that match your current filters, including the time range and search, as a spreadsheet file. Each row has the session’s source, who started it, its app and build, its device and why it ended.
Related: Test run history
Test runs have their own history and detail views under the Tests section. A test run’s page shows per-step results, a visual regression banner, and the build that was under test. Open it from a test session’s details, from a group, or from the tests dashboard.
Tips
- Sessions are scoped to your organization. You only see sessions started in your org.
- The device name and OS version are recorded when the session gets its device, so the history stays intact after a device is updated or removed.