New Group - When searching for a new user to add, user name is duplicated

[kbecciv]

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 staging.new.expensify.com
2. Sign into a valid account
3. Tap the green "Plus" icon on the bottom right
4. Tap "New Group"
5. Search for any user and tap on the search suggestion

Expected Result:

The users name should appear with a green check next to it

Actual Result:

The users name appears duplicated and the search becomes highlighted with a blue outline

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Web
• iOS
• Android
• Desktop App
• Mobile Web

Version Number: 1.1.42.3

Reproducible in staging?: Yes

Reproducible in production?: No

Email or phone of affected tester (no customers): mailto:emilio.utest@gmail.com

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Image.from.iOS.4.MP4

Expensify/Expensify Issue URL:

Issue reported by: Applause

Slack conversation:

View all open jobs on GitHub

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

[MelvinBot]

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

[NikkiWines]

I can reproduce this on dev, looking for what might have introduce this bug now 🕵️‍♀️

[NikkiWines]

Looks like #7530, which was it was just deployed to staging - confirming now

[NikkiWines]

Merge commit for #7530 is 80b7467fdfc5610259b3a7be33e5f603309c4be7

Checked out the merge commit prior to it 502412163a971e14f21e8cf18ebf2a3a6af25659 and confirmed the bug wasn't present.

cc: @AndrewGable @parasharrajat @eVoloshchak looks like #7530 has introduced this bug.

[parasharrajat]

Nope. It is not a regression. It is missed case from my PR #7986.

[NikkiWines]

Dropping to a daily since the fix PR has been merged

[chiragsalian]

CP-ing the PR to staging since the issue is a deploy blocker.

[chiragsalian]

The fix for this has been CP-d to staging. Can you retest @kbecciv.

[kbecciv]

Sure, we are going to test the CPs right now. Thank you @chiragsalian

[chiragsalian]

Once only a staging specific issue has been resolved we can close it out so that it's not repeated again as deploy blockers for the next checklist.