[HOLD] [LOW] [Splits] IOU - Re-creating Split Bill with anonymous gmail members causes IOU to crash

[lanitochka17]

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: 1.3.88-1

Reproducible in staging?: Yes

Reproducible in production?: No

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. Open New Expensify app
2. Log in with an expensifail account
3. Create Split Bill with gmail accounts with which there was no conversation history before
4. In the created group DM with these members, request the Split Bill again

Expected Result:

Re-creating Split Bill with anonymous gmail members should register IOU with no errors for both the re-request and the first

Actual Result:

Re-creating Split Bill with anonymous gmail members causes IOU to crash

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• Windows: Chrome
• MacOS: Desktop

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

Windows: Chrome

Bug6245877_1697922883003.Recording_1_Desktop.mp4

MacOS: Desktop

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @youssef-lr

Issue Owner

Current Issue Owner: @youssef-lr

[melvin-bot]

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

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

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

[pradeepmdk]

Proposal

Please re-state the problem that we are trying to solve in this issue.

IOU - Re-creating Split Bill with anonymous gmail members causes IOU to crash

What is the root cause of that problem?

the root cause when we call `SplitBill` its throwing the error

What changes do you think we should make in order to solve the problem?

this is backend issue.
because first time we re calling SplitBillAndOpenReport after that we are personal details with real account id. then we are calling SplitBill with those id when create split from report

onemore issue when we call SplitBillAndOpenReport it will return personal details without login key.

[mountiny]

This is an backend issue so not App deploy blocker technically

[flodnv]

@luacmartins @mountiny seems like you got this?

[mountiny]

Yes, this PR should fix it https://github.com/Expensify/Web-Expensify/pull/39344

[mountiny]

Or to be clearer this should have fixed it already https://github.com/Expensify/Web-Expensify/pull/39348 and the other pr is more of a clean up

@lanitochka17 @pradeepmdk can you please retest in staging

[pradeepmdk]

@mountiny just now tested still there

[mountiny]

@pradeepmdk do you need ot sign out and sign back in between the splits or you just do the request again right after it?

[pradeepmdk]

@mountiny i just request again

[mountiny]

@youssef-lr was debugging with Youssef and there are some other cases where this can fail due to the optimistic reports/ accountIDs, fix is underway

[youssef-lr]

Still held

[stephanieelliott]

Held now on https://github.com/Expensify/Expensify/issues/357867. I am going to be OOO til July 10 but not expecting much movement on this so will keep it assigned. If it needs attention in the meantime please reapply the BZ label

[stephanieelliott]

Still held on https://github.com/Expensify/Expensify/issues/357867

[youssef-lr]

Still held

[youssef-lr]

This is paused

[stephanieelliott]

Still held on https://github.com/Expensify/Expensify/issues/357867

[youssef-lr]

Same

[youssef-lr]

Same

[stephanieelliott]

Still held, looks like the blocking PR is moving though

[cead22]

@davidcardoza should this be on the #billpay project?

[stephanieelliott]

Seems like this has been fixed! Could not repro, split expense worked fine with no error or crash: