Web - Split - Scan bill split is created in one of the participants' chat instead of new group chat

[kavimuru]

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: v1.4.11-6
Reproducible in staging?: y
Reproducible in production?: n
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: Applause internal team
Slack conversation:

Action Performed:

1. Go to staging.new.expensify.com.
2. Click FAB > Request money > Scan.
3. Enter amount > Next.
4. Select two users that have existing IOUs > Click Split.
5. Create the bill split.

Expected Result:

The bill split is created in a new group chat with the selected users.

Actual Result:

The bill split is created in one of the participants' 1:1 DM instead of a new group chat.

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: mWeb Chrome
• iOS: Native
• [x ] iOS: mWeb Safari
• [x ] MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6309963_1702353483955.20231212_015403.mp4

View all open jobs on GitHub

[melvin-bot]

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

[github-actions]

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

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

[abzokhattab]

same as #32855

[MariaHCD]

This does look to be similar to #32855. Closing in favor of that issue.

[shubham1206agra]

@Julesssss @MariaHCD The fix does not seem to fix this issue. Please reopen this.
It opens wrong report actually

[Julesssss]

Hey @shubham1206agra just to confirm, even with the changes from the linked PR (which haven't yet been merged)?

[shubham1206agra]

Yes
It just opens the wrong report (more specific, of first participant)

[shubham1206agra]

Fix seems to be relatively easy. I will fix this in another PR

[Julesssss]

Thanks, reopening. I will assign you now @shubham1206agra.

@MariaHCD I'll try to keep an eye on this one but we have about 20+ blockers so it would be great if you could also keep on eye on any developments here. Thanks

[Julesssss]

Fix seems to be relatively easy. I will fix this in another PR

Hey @shubham1206agra just checking which PR you fixed this in?

[shubham1206agra]

#32918

[Julesssss]

Thanks, I just merged that fix. We'll verify the fix on staging