[$250] Error message appears when requesting IOU to a secondary login of a phone number

[m-natarajan]

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:
Reproducible in staging?: needs reproduction
Reproducible in production?: needs reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers): secondary email([email protected]) of a SMS number account ([email protected]).
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @quinthar
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1709348197580109

Action Performed:

1. Go to preexisting chat with secondary login email address [email protected] of SMS number [email protected]
2. Request money

Expected Result:

Able to request money

Actual Result:

Error message appears:
unexpected error creating this chat, please try again later. There is a previously existing chat between thest users

Workaround:

unknown

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

Add any screenshot/video evidence

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0189bc700718cf5a85
• Upwork Job ID: 1766165401103810560
• Last Price Increase: 2024-03-15

[melvin-bot]

Triggered auto assignment to @twisterdotcom (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[twisterdotcom]

I can't recreate this:

37835.mp4

@mallenexpensify laid out some steps for Needs Reproduction issues in Slack: https://expensify.slack.com/archives/C01SKUP7QR0/p1709232158079079?thread_ts=1709232107.784279&cid=C01SKUP7QR0

• GH created, $250 to start, bumped to $500 after 2 weeks
• Assigned C+ reviewed discussions and steps
• 3 contributors actively worked on finding the bug and steps
• New issue created for $500, same C+ assigned.
• The 3 contributors got first dibs for 48 hours to submit proposals before 'help wanted' was added.
• Once PR is merged, ask C+ to propose the payments they recommend for contributors who helped find the repro steps.

Cool, so it sounds like we want the community to help identify the reproduction steps. Gonna wait until the outcome of this conversation so as not to share some things more widely than they need to be shared: https://expensify.slack.com/archives/C01SKUP7QR0/p1709920757503339

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~0189bc700718cf5a85

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @c3024 (External)

[melvin-bot]

Upwork job price has been updated to $250

[c3024]

I could reproduce it by requesting money directly with the Request money from FAB instead of Start chat. It should be fixed from the backend.

Steps:

Pre-condition: User A has an existing chat with the primary login of User B

1. [User A] Click on FAB > Request Money
2. Input amount and click Next
3. Input the secondary login of User B and select the result displayed below
4. Click Request

Expected result: A money request from User A to User B created in the existing chat between User A and B

Actual result: A new chat is created between User A and secondary login of User B with an error from backend

TestSteps.mp4

[mallenexpensify]

Thanks @twisterdotcom , I created this internal issue to track, reckon it'll be a few weeks til I prioritize

• https://github.com/Expensify/Expensify/issues/377295

I think the first step, after BZ isn't able to reproduce, would be to add the Internal label to ask the C+ if they can and, if so, to provide additional details. Which, for this example, would have had @c3024 able to reproduce. Then you'd attempt again to confirm then the issue would move on. (and... sorry @c3024 , since you're C+ assigned, you wouldn't get compensation for being able to reproduce).

[melvin-bot]

@twisterdotcom, @c3024 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[twisterdotcom]

Ah nice, well okay. Let me see if I can reproduce with that way too @c3024.

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[twisterdotcom]

Yeah, this is odd, the bug is real!

1. Open staging.new.expensify.com
2. Use the green plus button to Request Money > $X > [email protected]
3. Witness the error.

866608899df455ea-LHR

406 Chat report with these participants already exists with different ID

86660889ce3b55ea-LHR

404 Report not found

37835.mp4

As @c3024 says, likely internal.

[twisterdotcom]

Waiting on an internal engineer

[mvtglobally]

Issue not reproducible during KI retests. (First week)

[twisterdotcom]

The bug still exists:

[mvtglobally]

Issue not reproducible during KI retests. (Second week)

[twisterdotcom]

It still very much exists. @mvtglobally what flow are you testing? I get this every single time I request money/submit expense to [email protected] using the FAB.

[mvtglobally]

What are we missing?

1714152746057.bandicam_2024-04-26_23-00-53-208.mp4

1714156931585.Screen_Recording_2024-04-26_at_21.39.02.mp4

[c3024]

@mvtglobally In the second video, you should already have chat with David's sms before requesting money from their secondary login.

Flow in the first video does not reproduce this bug. You should start with submit expense from FAB as mentioned here

[mvtglobally]

@c3024

Can you pls comment with the exact steps from a Brand new account. Unfortunately, we need to use new accounts as messaging David's sms is not a viable option

[twisterdotcom]

1. Create a new account
2. Create a DM chat with [email protected]
3. Create a request (submit expense) to [email protected]

[mvtglobally]

@twisterdotcom Are you able to reproduce it with any other account rather than [email protected] or [email protected]

It is not reproducible if we use other SMS and email accounts

[twisterdotcom]

I literally just created an account for +447876868752 with a secondary login of [email protected] and recreated the bug straight away:

37835.mp4

The bug is real and definitely exists.

[mvtglobally]

Issue not reproducible during KI retests. (Third week)

1715962343820.bandicam_2024-05-17_21-41-04-448.mp4

1715967174957.Screen_Recording_2024-05-17_at_13.29.34.mp4

[twisterdotcom]

@mvtglobally could you please test with the account I provided from above? So try creating an expense with [email protected]?

[mvtglobally]

looks like we are only able to reproduce if there is an existing chat with the primary login of a user

Recording.521.mp4

[c3024]

Yes, that is what I mentioned as a pre-condition here.

Pre-condition: User A has an existing chat with the primary login of User B

[twisterdotcom]

Great, do we think this is still Internal now then?

[c3024]

Great, do we think this is still Internal now then?

I think so.

[mvtglobally]

Issue not reproducible during KI retests. (Fifth week)

[twisterdotcom]

Okay, finally I cannot reproduce. I have no idea how or when this was fixed though.