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
Limrun iOS fill reports success but drops non-ASCII text #3819
On a Limrun iOS simulator, fill / typeText reports success and does not insert Chinese. ASCII on the same focused field works. setElementValue inserts the Chinese and the app reads it back.
packages/provider-limrun/src/ios.tsfill() taps the field, sends Cmd-A, then typeText. That is hardware key events. Chinese has no key code, so the call returns "Text typed" and the field is unchanged.
e2e documents locator.fill as setting the value with no key events (pressSequentially is the keystroke path). @e2e-dev/mobile and @e2e-dev/limrun hit this through agent-device.
Triage: bug; actionable without more input from you. Confirmed on main: the Limrun iOS fill in packages/provider-limrun/src/ios.ts selects with Cmd-A and then sends typeText, which is key events only. Text with no key code is dropped, and the call still reports success. The fix moves fill to setElementValue after focus, including for "". type keeps the key-event path. An agent can pick this up.
Fill focused the field, selected its contents with Command-A, and then sent the string as hardware key events. Characters with no key code never become a key event, so they are dropped while the call still succeeds.
After text-entry focus arrives, fill writes the whole string with one setElementValue call, including an empty string and characters that have no hardware key.
Activity
thymikee commentedon Oct 20, 2026
Triage: bug; actionable without more input from you. Confirmed on main: the Limrun iOS
fillinpackages/provider-limrun/src/ios.tsselects with Cmd-A and then sendstypeText, which is key events only. Text with no key code is dropped, and the call still reports success. The fix movesfilltosetElementValueafter focus, including for"".typekeeps the key-event path. An agent can pick this up.mvanhorn commentedon Oct 21, 2026
Fill focused the field, selected its contents with Command-A, and then sent the string as hardware key events. Characters with no key code never become a key event, so they are dropped while the call still succeeds.
After text-entry focus arrives, fill writes the whole string with one setElementValue call, including an empty string and characters that have no hardware key.
#3863