Limrun iOS fill reports success but drops non-ASCII text
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 87/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- ios, mobile-dev, typescript
Research direction
Read packages/provider-limrun/src/ios.ts and inspect fill() alongside the existing setElementValue and typeText paths. Check how the iOS provider handles focusing the field, clearing it, and setting an empty value. Done when fill() inserts non-ASCII text through the value-setting path, including for an empty string, while type() and pressSequentially continue using keystrokes; verify with the reproduction steps in the issue.
Written by the indexing model from the issue text.
Description
What happened
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.ts fill() 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.
Reproduction
App: https://github.com/limrun-inc/sample-native-app (simulator build). Field nameField, button greetButton.
lim ios type "Ada"onnameField, tapgreetButton.
Field isAda. Heading isHello, Ada!. Log:greeted Ada.- Focus the field, Cmd-A,
lim ios type "你好", tap the button.
CLI printsText typed. Field staysAda. Heading staysHello, Ada!. - Clear the field,
lim ios type "你好".
CLI printsText typed. Field stays the placeholderYour name. lim ios type "Hello"on that same field.
Field becomesHello.lim ios set-text "你好" --ax-unique-id nameField, tap the button.
Field is你好. Heading isHello, 你好!. Log:greeted 你好.
Expected
fill should call setElementValue after focus, including for "". Leave type() / pressSequentially on typeText.
- Dominant language
- TypeScript
- Stars
- 5k
- Forks
- 334
- Avg merge
- 12h 13m
- Merged PRs (30d)
- 723
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from callstack/agent-device
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
callstack/agent-device#1869 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
callstack/agent-device#3851 ·
Maintainers usually reply within 1 day
-
feat(hardware-button): press phone volume and power buttons on Android and iOSPossibly taken @thymikee claimed this today. Openneeds-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
callstack/agent-device#3848 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
callstack/agent-device#3844 ·
Maintainers usually reply within 1 day
-
press/click: refuse a zero-area target instead of tapping its originPossibly taken @faresrafat3 claimed this today. Openbug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 20/100
callstack/agent-device#3841 ·
Maintainers usually reply within 1 day
All issues in callstack/agent-device
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
diegosouzapw/OmniRoute#17386 ·
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
area/dashboard kind/bug kind/bug-qa QA/dev-automation
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
vybestack/llxprt-code#3917 · 1 comment ·
Maintainers usually reply within 1 day
-
api-parity
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
IBM/carbon-components-ember#1157 ·
Maintainers usually reply within 1 day