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 ffff797
Browse filesBrowse the repository at this point in the historyBrowse files
fix(interaction): keep the screenshot readback from failing a delivered tap
Nothing after a resolved dispatch throws out of the evidence lane anymore: a
decode, read, import or cleanup failure yields no evidence, because a throwing
readback reported a delivered tap as failed and a PIN caller would re-enter
the digit. The after-frame settle honors the request signal. Both frames
decode in the codec worker, the guard audits a missing descriptor instead of
skipping it, the docs say the readback is best-effort, and the delivered-tap
tests record the tap.
Co-Authored-By: Claude Code <[email protected]>
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
@@ -499,7 +499,7 @@ agent-device gesture tap 80 300 200 450 --count 20 --pause-ms 100 # repeated two
499
499
500
500
If rotation stops repeated iOS presses, inspect the screen before continuing with the remaining presses.
501
501
502
-
A successful `click` or `press` means the action was sent to where the command found the target. It does not confirm that the element received it or that the screen changed. When the next step depends on it, add `--verify` (reports `changedFromBefore`), add `--settle` (returns the diff once the UI goes quiet), or follow with `wait <selector>`. When the target lives outside the accessibility tree (a PIN keypad), `--verify` compares empty trees, so add `--expect-screenshot-diff` on `press`/`click` instead: the command compares screenshots taken right before the dispatch and after it settles briefly, and warns when they match. Before retrying a failed interaction, see [Retry after a failed command](#retry-after-a-failed-command).
502
+
A successful `click` or `press` means the action was sent to where the command found the target. It does not confirm that the element received it or that the screen changed. When the next step depends on it, add `--verify` (reports `changedFromBefore`), add `--settle` (returns the diff once the UI goes quiet), or follow with `wait <selector>`. When the target lives outside the accessibility tree (a PIN keypad), `--verify` compares empty trees, so add `--expect-screenshot-diff` on `press`/`click` instead: the command compares screenshots taken right before the dispatch and after it settles briefly, and warns when they match. The readback is best-effort: on a backend without screenshot capture, or when a capture or comparison fails, the response carries neither `screenshotDiff` nor a warning and claims nothing about the screen. Before retrying a failed interaction, see [Retry after a failed command](#retry-after-a-failed-command).
503
503
504
504
A `click` or `press` whose target the daemon resolves to a point (`@ref` or selector) re-checks that target's position before dispatching when the session's previous action animated the screen, and dispatches where it came to rest. When that check cannot confirm a stable position — the target was still moving, or a re-check could not measure it — the command refuses with `target_still_moving` and `dispatched: no`: nothing was dispatched, the point the command resolved is in `error.details.rect`, and where the target was last seen is in `error.details.movedToRect` when that last look measured one. Run `wait <selector>` on the target and retry the same command, or add `--settle` so the action waits for the UI to go quiet. A refused `@ref` press needs a fresh `snapshot -i` and a selector, because the wait retires the ref. Two dispatch paths hand off before the check: a press at raw coordinates has no resolved target to re-check, and a dispatch the backend performs on the element itself — `click @ref` on a backend with element dispatch, or a Maestro non-hittable coordinate fallback — goes to that backend rather than through a resolved point. The re-check stops when the request is canceled or reaches its deadline, and nothing is dispatched (`dispatched: no`): a canceled request fails with `details.reason: request_canceled`, and a request out of time with `details.reason: daemon_request_timeout`.
0 commit comments