Sessions
Sessions group captured traffic into named runs so you can keep test cases separate, review history, and export precise slices of data.
How sessions work
Trace creates a session automatically each time you start capture. The session tracks:
- Name – optional label you assign (defaults to a timestamp-based display name)
- Start time – when capture began
- End time – when capture was stopped (active sessions have no end time)
- Request count – number of captured requests in the session
- Total data transferred – cumulative bytes across all requests
Sessions are stored in the shared App Group database and persist across app restarts.
Start a new session
- Tap the capture toggle to stop any active session.
- Tap the capture toggle again to start a fresh session.
Each start creates a new session entry. The previous session's data remains available for review.
Name a session
- Open the session list from the Network tab toolbar.
- Tap a session to select it, then tap Rename.
- Enter a descriptive name (for example,
checkout-flow-v2orlogin-regression).
Named sessions are easier to identify when exporting or sharing.
Switch between sessions
Open the session picker from the Network list toolbar. Tap any session to switch the list to show only that session's traffic. The active capture session is marked with a running indicator.
Group the list by session
Enable Group by Session in the Network list settings to show requests separated by their capture run. This is useful when you have multiple sessions and want a timeline view.
Export a single session
Exporting a specific session avoids including unrelated traffic from other runs.
- Open the session list.
- Long-press or swipe a session to reveal export options.
- Choose Export as HAR or use the share action.
See Exporting sessions for all available export formats.
Delete a session
Swipe a session entry left and tap Delete, or use Settings → Storage & Cleanup to bulk-remove old sessions.
Tip
Name sessions by feature or test case before you start capturing. It is easier to do it up front than to rename after the fact when you have multiple runs.