[$1000] Users list not showing on split confirm

[amyevans]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

This is a follow up issue from #17349 (comment)

Action Performed:

1. Open any group chat on web app
2. Click + icon > Split bill
3. Copy url from address bar (url should be like this format: http://localhost:8080/split/new/xxx)
4. Open desktop app
5. Paste url in new tab and open desktop app from popup
6. Enter any amount and click Next

Expected Result:

User list is present

Actual Result:

User list is missing

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:
Reproducible in staging?:
Reproducible in production?:
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

bug.mov

Expensify/Expensify Issue URL:
Issue reported by: @aimane-chnaif
Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0108aaabc2bc8e4aeb
• Upwork Job ID: 1665886572966985728
• Last Price Increase: 2023-06-06

[melvin-bot]

Triggered auto assignment to @miljakljajic (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

[amyevans]

@jczekalski please comment on the issue so I can assign you

[jczekalski]

@amyevans

[melvin-bot]

@amyevans, @miljakljajic, @jczekalski, @aimane-chnaif Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[miljakljajic]

Apologies - I have been at EC3 so only just getting to this today. I am OOO reapplying the label so that we can reproduce this - can we get some more detailed reproduction steps for the next BZ member @amyevans - I have tried to reproduce this using your comment above but I'm not able to. Can you break it down step by step for the next person?

I'll assign it to you for now and then can you reapply the label when you've updated the steps? Thank you!