mirror of
https://github.com/callstack/agent-device.git
synced 2026-09-14 20:06:34 +08:00
Michał Pierzchała
c78bfd1e62
* fix: guide agents past iOS keyboard dismissal and get-text guesses Tonight's benchmark leaderboard showed two recurring agent-UX misses: keyboard dismiss failing after fill (5x, now the #1 failed command) and get-text guessed as a command name (1x). - iOS keyboardDismiss now returns a hint explaining the on-screen keyboard does not block agent-device interactions, so agents should press the next target directly instead of retrying dismiss, and use keyboard enter only when submission is actually wanted. - help manual-qa and help workflow recovery text no longer teach the false "dismiss to unblock the target" pattern. - The command-suggestion curated map now maps get-text/gettext/get_text to the real get text command shape; the generic edit-distance fallback did not produce any suggestion for these guesses. * fix: soften keyboard guidance for genuinely covered targets Review on #1173 flagged the unconditional "does not block" claim as false for targets visually covered by the keyboard: direct-selector press resolution is isHittable-gated and falls through to ELEMENT_NOT_FOUND, the tree path allows non-hittable taps with only a no-visible-effect hint, and bottom-pinned-button-under-keyboard (#291/#469/#957) is a real case where dismissal was the remedy. All three strings (runner hint, help manual-qa, help workflow) now say the keyboard USUALLY does not block presses and name concrete fallbacks: scroll the target into view, or keyboard enter when submission is wanted.