Workspace is not selected as participant when a manual request is created

[marcochavezf]

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

---

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
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:

Coming from here

Action Performed:

1. In a workspace chat, click on "Request money"
2. Select manua, enter any amount
3. Click on "Next" button

Expected Result:

The confirmation page should show the workspace in the field "to"

Actual Result:

Nothing is shown as a selected participant, and the "Request" button is disabled

Screen.Recording.2023-10-19.at.4.04.16.p.m.mov

Workaround:

No workaround

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

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

View all open jobs on GitHub

[melvin-bot]

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

[thienlnam]

In the thread, we found that it was likely caused by #27547

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

Current assignee @marcochavezf is eligible for the Engineering assigner, not assigning anyone new.

[marcochavezf]

PR that introduced the regression was reverted here. @Christinadobrzyn could you handle the payment for @hoangzinh? Since help us to test another PR and caught the original fix wasn't enough to fix the regression.

[Christinadobrzyn]

Yep! @marcochavezf and @hoangzinh does $500 or $250 sound good for payment? Not sure how much work was done on this. Thanks!

[hoangzinh]

I'm happy with $125 because it doesn't have much effort

[lukemorawski]

@thienlnam @marcochavezf I think I have the solution to this problem so #27547 could be merged again.

[thienlnam]

@lukemorawski Could you create another PR with the fix and then the original reviewers can take another look at it?

[melvin-bot]

This issue has not been updated in over 15 days. @marcochavezf, @hoangzinh, @Christinadobrzyn eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

[melvin-bot]

@marcochavezf, @hoangzinh, @Christinadobrzyn, this Monthly task hasn't been acted upon in 6 weeks; closing.

If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.