Workspace - Phone number shown twice when try to search on Workspace - Invite Members.

[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. Login to ND
2. Click on the Search icon
3. Type an invalid phone number e.g. +444
4. Type a valid phone number e.g. +1 (500) 555-0007
   Try to search step 4:
   Search Page
   New group page
   New chat page
   Send Money
   Request Money
   Split Bill

Expected Result:

For all searching phone number e.g. +1 (500) 555-0007 should be show once

Actual Result:

The phone number shown twice when try to search on Workspace - Invite Members.

Workaround:

Unknown

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

Reproducible in staging?: Yes

Reproducible in production?: Yes

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

Bug6041645_18103_Desktop.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[MelvinBot]

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

[MelvinBot]

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

[laurenreidexpensify]

I am struggling to repro this on prod or staging on web chrome

[laurenreidexpensify]

Still can't reproduce. @kbecciv can you confirm if this is still reproducible your side? thanks

[melvin-bot]

@laurenreidexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

[kbecciv]

@laurenreidexpensify Checking with team, will get back to you shortly.

[kbecciv]

Issue is no longer reproductible

Screen.Recording.2023-05-08.at.5.45.45.PM.mp4

[laurenreidexpensify]

Closing as no longer reproducible.

[strepanier03]

@kbecciv - I am working on writing down a process for investigating non-reproducible bugs.

Can you help me out here and let me know the email address that was used when the bug occurred originally? I will be doing some extra investigation to see if there is a way we can further document bugs that are infrequent or not consistently reproducible. Having the email should help me isolate logs pertaining to the behavior reported.

Thanks!

[kbecciv]

I need to check May Cycle and see which email was used by tester. Will update you shortly

[kbecciv]

@strepanier03 Tester used: rybkina+007@gmail.com