[$1000] Unexpected error while splitting money- After task history- mobile number

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Action Performed:

Pre-requisite: There must be a task history over user A and user B. Please assign task from User A to User B and send some messages. User B must be a phone number.
1 Login as User A and click on + button and click on split money
2 Set amount and description and select User B
3. Split money and verify if you get error

Expected Result:

There should be no error in splitting money with registered users.

Actual Result:

Got these errors : “There is a previously existing chat between these users.”
“Auth GetEmailByAccountID returned an error” and “Unexpected error requesting money, please try again later”
I got error with both registered and unregistered mobile numbers

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

Recording.2288.mp4

reply-kavi.muru.1.mp4

Expensify/Expensify Issue URL:
Issue reported by: @avi-shek-jha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1688104145295479

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~016b1c3dd2f7daeaad
• Upwork Job ID: 1676297367694114816
• Last Price Increase: 2023-07-25

[melvin-bot]

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

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~016b1c3dd2f7daeaad

[melvin-bot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @abdulrahuman5196 (Internal)

[mallenexpensify]

Updated OP to make it clear at the beginning that User B needs to be a phone number. I was able to reproduce,

@abdulrahuman5196 , can you also test to see if you're able to reproduce then propose if this should be internal or external? thx

[melvin-bot]

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

[abdulrahuman5196]

Will check and update in the morning

[abdulrahuman5196]

@mallenexpensify I was able to reproduce this issue. I think there should be some issue in what report Id we are using for split in frontend, since it is not expected to create a new report since we already have a chat with the user created by the task.
We can open it for external, there could be some internal work. But the investigation place to start is in frontend.

[bernhardoj]

Same root cause with #22433

[melvin-bot]

Current assignee @mallenexpensify is eligible for the External assigner, not assigning anyone new.

[melvin-bot]

Current assignee @abdulrahuman5196 is eligible for the External assigner, not assigning anyone new.

[mallenexpensify]

Made External, dropped a comment on #22433 for Kadie to keep tabs on this, thanks for the comment @bernhardoj

[abdulrahuman5196]

I think both the issues are related from the root cause from @bernhardoj. I will review the proposal here and re-check if the solution solves both the issues and update back.
Meanwhile, @bernhardoj could you kindly post your proposal here as well specific to this issue?

[abdulrahuman5196]

I had already posted in open source channel days back, missed to paste the reference here https://expensify.slack.com/archives/C01GTK53T8Q/p1692383613454819

But still no update @mallenexpensify

[melvin-bot]

@mallenexpensify, @abdulrahuman5196 Eep! 4 days overdue now. Issues have feelings too...

[mallenexpensify]

Thanks @abdulrahuman5196 , I posted again and tagged the @engineering-team, to see if that helps. I'm guessing you're unable to. Let's see if we get some 🎣

[abdulrahuman5196]

This needs to be on hold as discussed here https://expensify.slack.com/archives/C01GTK53T8Q/p1693412993417589?thread_ts=1692383613.454819&cid=C01GTK53T8Q

cc: @puneetlath @mallenexpensify

[mallenexpensify]

Put on Hold, will add issue number once it's dropped in the thread. https://expensify.slack.com/archives/C01GTK53T8Q/p1693818288598599?thread_ts=1692383613.454819&cid=C01GTK53T8Q

[mallenexpensify]

Checking again for issue link
https://expensify.slack.com/archives/C01GTK53T8Q/p1694416424585289?thread_ts=1692383613.454819&cid=C01GTK53T8Q

[mallenexpensify]

Aldo commented, we're on hold for the below, title updated

• [HOLD for payment 2023-10-05] Report - The request money is broken for "unknown" accounts without login information #22480

[mallenexpensify]

• [HOLD for payment 2023-10-05] Report - The request money is broken for "unknown" accounts without login information #22480 (comment)

Made PR ready for review

Held issue is moving along

[mallenexpensify]

Off hold, @kavimuru can you see if you can still reproduce?
Thx

[mallenexpensify]

@kavimuru , are you able to reproduce? Thx

[kavimuru]

@mallenexpensify I am not able to reproduce

Recording.1629.mp4

[mallenexpensify]

Closing, unable to reproduce and a lot of shit's changed with split and associated flow.