Number typing error when using Vietnamese Telex keyboard

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Go to FAB, then select "Request Money" or "Split bill"
2. Input an amount (e.g., "123")
3. Switch percussion from US keyboard to Vietnamese Telex
4. Then continue to enter the amount until it can't be entered anymore

   Expected Result:

   Can enter or edit money when in Vietnamese Telex keyboard

   Actual Result:

   When enter the full amount, it will be deleted. Can't enter amount while in Vietnamese Telex keyboard.

   Workaround:

   Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Which of our officially supported platforms is this issue occurring on?

• [ ] Android / native
• [ ] Android / Chrome
• [ ] iOS / native
• [ ] iOS / Safari
• [x] MacOS / Chrome / Safari
• [ ] MacOS / Desktop

Version Number: Reproducible in staging?: needs reproduction Reproducible in production?: needs reproduction If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs: https://stackoverflow.com/c/expensify/questions/4856 Notes/Photos/Videos: Any additional supporting documentation

split_bill.webm

request money.webm

Expensify/Expensify Issue URL: Issue reported by: @Le Thi Thu Thuy Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1691744296819669

View all open jobs on GitHub

[melvin-bot[bot]]

Triggered auto assignment to @kevinksullivan (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot[bot]]

Bug0 Triage Checklist (Main S/O)

• [ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• [ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• [ ] This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• [ ] This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• [ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[kevinksullivan]

https://expensify.slack.com/archives/C049HHMV9SM/p1692655258166639?thread_ts=1691744296.819669&cid=C049HHMV9SM