previously stored search input is sent to the backend instead of the latest value entered by the user

[m-natarajan]

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

---

Version Number: 1.4.24-4
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
Expensify/Expensify Issue URL:
Issue reported by: @youssef-lr
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1704921995746249

Action Performed:

1. click on "search" icon beside the avatar
2. Type user 1
3. Check the API

Expected Result:

Latest entered input should be sent to backend

Actual Result:

Previously stored result is sent to backend

Workaround:

unknown

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Recording.2653.mp4

Screen.Recording.2024-01-10.at.22.23.55.mov

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0187544a07fd9a4b27
• Upwork Job ID: 1745445129843707904
• Last Price Increase: 2024-01-11

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~0187544a07fd9a4b27

[melvin-bot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @rushatgabhane (Internal)

[melvin-bot]

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

[rushatgabhane]

this can be external (if we want to)

[youssef-lr]

I have a fix included in an ongoing draft PR but figured I ship this separately sooner.

[mallenexpensify]

@rushatgabhane should be assigned as C+, even if we fix this internally..... right?

[youssef-lr]

Actually the PR I was planning to fix this in is almost ready, so I'll include the fix in there instead of fixing this separately.

@rushatgabhane should I assign you for reviewing it? We're adding the possibility to return personalDetails from SearchForReports so we can display proper avatars/display names of any user we search for.

[mallenexpensify]

Do you have a link to the PR @youssef-lr ? Thx

[youssef-lr]

#34400

[rushatgabhane]

@youssef-lr yeah sure you can assign it to me

[mallenexpensify]

Assigned @rushatgabhane

[youssef-lr]

Backend PRs are still under review.

[youssef-lr]

remaining PRs still in the works.

[youssef-lr]

Same.

[melvin-bot]

@youssef-lr @mallenexpensify @rushatgabhane this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!

[melvin-bot]

@youssef-lr, @mallenexpensify, @rushatgabhane Eep! 4 days overdue now. Issues have feelings too...

[youssef-lr]

Bumped the reviewer

[youssef-lr]

Looks like this was fixed in this PR unintentionally.