You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 1edb276
Browse filesBrowse the repository at this point in the historyBrowse files
fix(revyl): replay only unreachable or transient requests, and fix the docs
A timed-out or canceled request is no longer replayed, and the replay reads
the request's own route. The iOS docs name the accessibility tree and say
back is Android-only, and the cloud page keeps Limrun's allocating commands
apart from Revyl's.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Copy file name to clipboardExpand all lines: website/docs/docs/device-clouds.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ Use a device cloud or farm when an agent needs to drive a hosted mobile device w
26
26
27
27
## Shared workflow
28
28
29
-
Every provider runs through the local `agent-device` daemon. `connect` checks your credentials and configuration, then saves non-secret connection state; it does not allocate a device. BrowserStack, AWS Device Farm, and TestMu AI allocate a hosted session on `open`. Limrun and Revyl allocate an instance on the first device command, such as `snapshot` or `open`.
29
+
Every provider runs through the local `agent-device` daemon. `connect` checks your credentials and configuration, then saves non-secret connection state; it does not allocate a device. BrowserStack, AWS Device Farm, and TestMu AI allocate a hosted session on `open`. Limrun allocates an instance on the first device command, such as `install` or`open`. Revyl allocates a device on the first device command, usually`open`.
0 commit comments