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 cee2da1
Browse filesBrowse the repository at this point in the historyBrowse files
fix(record): record a remote client's default recording on the daemon host (#3696)
* fix(record): record a remote client's default recording on the daemon host
A remote record start without a path left the default name to the daemon,
which resolved ./recording-<ts>.mp4 against the client's cwd and failed
with EACCES on the daemon host. The client now sends its local destination
without an extension; the daemon completes it with the session platform's
extension, records to a temp path on its own host, and the client downloads
the file there on record stop.
Found while driving an EAS cloud simulator session.
* fix(record): choose the remote default recording path in the daemon record handler
Keep resolveRecordingOutputPaths transport-free: capture-kit picks the
extension and resolves paths, and only the daemon knows a request came
from a remote client. Document where a remote record start without a
path downloads.
Copy file name to clipboardExpand all lines: website/docs/docs/commands.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
@@ -124,7 +124,7 @@ Remote daemons and tenants:
124
124
125
125
-`--tenant`, `--session-isolation tenant`, `--run-id`, and `--lease-id` enforce lease admission on tenant-scoped daemons.
126
126
-`--daemon-base-url http(s)://host:port[/base-path]` calls a remote HTTP daemon directly instead of starting a local one. Add `--daemon-auth-token <token>` (or `AGENT_DEVICE_DAEMON_AUTH_TOKEN`) for non-loopback daemon URLs.
127
-
- Screenshots and recordings from a remote daemon are downloaded to the path you pass, so `screenshot page.png` and `record start session.mp4` work as they do locally.
127
+
- Screenshots and recordings from a remote daemon are downloaded to the path you pass, so `screenshot page.png` and `record start session.mp4` work as they do locally.`record start` without a path downloads to `recording-<timestamp>.mp4` (`.webm` on web) in your working directory.
128
128
- To drive a Mac's simulators and devices from another machine, see [Remote Proxy](/docs/remote-proxy). For hosted devices in CI, see [BrowserStack](/docs/browserstack), [AWS Device Farm](/docs/aws-device-farm), or [TestMu AI](/docs/testmu). For `connect --remote-config`, see [Remote Metro workflow](#remote-metro-workflow).
0 commit comments