Skip to content

docs(website): --lease waits for a starting worker (#991) #1002

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
V3RON merged 1 commit into from
Oct 25, 2026
Merged

docs(website): --lease waits for a starting worker (#991) #1002

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/src/content/docs/docs/using-devices/working-with-a-device.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ simlock --gateway simctl --lease 3f81a2c4-9b7d-4e21-8a55-1c0e6f2d7b93.lse_9f2c6a
- `--lease <lease-id>` names which lease the command runs under. Put it right after `simctl` or `adb`. You can leave it out when you hold exactly one lease. Against a worker it is accepted and ignored.
- File paths in the arguments are paths on the worker, not on your machine. `simctl install` needs the app to exist on the worker already.
- Commands that need a terminal, such as a bare `adb shell`, are refused. Input piped to the command is sent once.
- Right after a worker restarts, the gateway hides its leases from `lease.list` and `lease.get` until the worker is no longer `starting`. That is the worker's startup checks plus one gateway refresh: usually seconds, up to about a minute, because a platform's startup read is capped at 60 seconds. In that window the command fails with `No lease is held by <your id>` although the lease stands. Do not request a new device on that message: wait a minute and run the command again.
- Right after a worker restarts, the gateway hides its leases from `lease.list` and `lease.get` until the worker is no longer `starting`. That is the worker's startup checks plus one gateway refresh: usually seconds, up to about a minute, because a platform's startup read is capped at 60 seconds. In that window the command fails with `No lease is held by <your id>` although the lease stands. Do not request a new device on that message: wait a minute and run the command again. With `--lease <lease-id>` you do not see the error: the command skips the lookup, waits for the worker to finish starting, and then runs, up to about a minute later.

## Commands Simlock refuses

Expand Down
Loading