Selecting user doesn't clear input text from search field on Split Bill page

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Action Performed:

1. Click on 'FAB' icon
2. Click on 'Split bill' link
3. Enter amount & click on 'Next' button
4. Search a user in the input field
5. Select the user

Expected Result:

Text from the input field should be cleared

Actual Result:

Text from the input field is not cleared

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.37-1
Reproducible in staging?: y
Reproducible in production?: n
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

Screencast.from.2023-07-05.22-02-39.mp4

Recording.1171.mp4

Expensify/Expensify Issue URL:
Issue reported by: @Natnael-Guchima
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1688584083890729

View all open jobs on GitHub

[melvin-bot]

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

[OSBotify]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Triggered auto assignment to @marcaaron (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[marcaaron]

I think this is possibly related to: #20271

cc @multijump @Julesssss @allroundexperts

[allroundexperts]

@marcaaron Nops. This is a result of #20736

[allroundexperts]

The removal of following in #20736 caused this.

if (!isOptionInList) {
  setSearchTerm('');
}

[marcaaron]

@dukenv0307 Are you able to fix this quickly?

@Julesssss I'm not sure, but maybe you will want to just revert that PR to get the deploy unblocked.

[fedirjh]

@marcaaron I am not sure if this a blocker, This is the new behavior that we discussed in this thread

[greg-schroeder]

Okay so it can't be expected behavior and also a deploy blocker. The thread linked above indicates this is actually expected

[greg-schroeder]

I pinged in the thread to get some additional 👀

[Julesssss]

Excellent, thanks all.