[$1000] Gboard swipe on backspace to delete text doesn’t work properly on message box

[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 any chat,
2. Type long text,
3. Swipe on backspace key back and forth.

Expected Result:

Text selection should change according to backspace swipe and selected text should be deleted

Actual Result:

Text selection freezes while adjusting swipe length and text isn’t deleted

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
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.13-3
Reproducible in staging?: Y
Reproducible in production?: Y
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

Swipe.mp4

az_recorder_20230512_172450.1.mp4

Expensify/Expensify Issue URL:
Issue reported by: @Nishan-Chhetri
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1683868631422409

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~016ab890488ee034d1
• Upwork Job ID: 1660646653359689728
• Last Price Increase: 2023-05-22

[melvin-bot]

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

[melvin-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

[melvin-bot]

@sonialiap Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[sonialiap]

will triage tomorrow

[sonialiap]

I can reproduce this bug on an android device

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~016ab890488ee034d1

[melvin-bot]

Current assignee @sonialiap is eligible for the External assigner, not assigning anyone new.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane (External)

[melvin-bot]

Triggered auto assignment to @pecanoro (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

[naveensingh]

This bug is very similar to #8349 and is resolved by an existing RN pull request Expensify/react-native#55.
I have tested the fix and can confirm that it works as expected. There are no other changes required.

[pecanoro]

Two totally unrelated comments:

• I didn't even know you could do that on Android and I had Android phones for more than 15 years 😄
• I completely agree it's extremely similar and the fact that this was proposed to be fixed in RN before even this was reported, I am going to close it.