Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[LOW] [Splits] [$500] Request – Unable to Request money twice to the same user you have no conversation with. #33487

Closed
3 of 6 tasks
izarutskaya opened this issue Dec 22, 2023 · 46 comments
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. External Added to denote the issue can be worked on by a contributor Help Wanted Apply this label when an issue is open to proposals by contributors Weekly KSv2

Comments

@izarutskaya
Copy link

izarutskaya commented Dec 22, 2023

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: v1.4.16-1
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
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation: @

Prerequisite: The new account you're requesting money from must have an updated user name in NewDot, ie. first name = Matt, last = test, as seen in Matt A's vid below.

Action Performed:

  1. Go to https://staging.new.expensify.com/
  2. Log in
  3. Click the FAB menu in LHN
  4. Click on "Request money" Manual.
  5. Enter an amount into the BNP and click Next
  6. Enter an email of the user you have no conversation with and click on the “Request …”
  7. Go back to the LHN and create one more request with the same user (repeat steps 3-6)

Expected Result:

Two requests are in DM with the user you just sent a request to.

Actual Result:

Error appears when create the second request.

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

Bug6323555_1703223322049.Unable_to_Request_money_twice_to_the_new_user.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01497816ffe49c0bd0
  • Upwork Job ID: 1738134853342339072
  • Last Price Increase: 2024-04-20
@izarutskaya izarutskaya added External Added to denote the issue can be worked on by a contributor Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Dec 22, 2023
@melvin-bot melvin-bot bot changed the title Request – Unable to Request money twice to the same user you have no conversation with. [$500] Request – Unable to Request money twice to the same user you have no conversation with. Dec 22, 2023
Copy link

melvin-bot bot commented Dec 22, 2023

Job added to Upwork: https://www.upwork.com/jobs/~01497816ffe49c0bd0

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Dec 22, 2023
Copy link

melvin-bot bot commented Dec 22, 2023

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

Copy link

melvin-bot bot commented Dec 22, 2023

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

Copy link

melvin-bot bot commented Dec 22, 2023

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

@danieleverest
Copy link

danieleverest commented Dec 22, 2023

This error is still exist? I can't find this error. It works well.

Copy link

melvin-bot bot commented Dec 22, 2023

📣 @handaniel214! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

  1. Make sure you've read and understood the contributing guidelines.
  2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
  3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
  4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
    Screen Shot 2022-11-16 at 4 42 54 PM
    Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

@bernhardoj
Copy link
Contributor

Proposal

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

Requesting money twice to the same user that we haven't chatted with before will give an error.

What is the root cause of that problem?

This has the same root cause as #22031 (comment).

In summary, when we create a money request with a user that we haven't chatted with before, we don't have their login yet. If we try to search for that same user when selecting the money request participant, we won't be able to find it and it will create a new optimistic account (with a different accountID) because we filter out any user that doesn't have a login.

// We're only picking personal details that have logins set
// This is a temporary fix for all the logic that's been breaking because of the new privacy changes
// See https://github.com/Expensify/Expensify/issues/293465 for more context
// Moreover, we should not override the personalDetails object, otherwise the createOption util won't work properly, it returns incorrect tooltipText
const havingLoginPersonalDetails = !includeP2P ? {} : _.pick(personalDetails, (detail) => Boolean(detail.login) && !detail.isOptimisticPersonalDetail);

Because the accountID is different, we created a new chat report and it will throw an error because we already have an existing chat with that user.

In #22031, we are holding for #22480, but #22480 actually doesn't fix #22031. In #22480, we only fix an issue where the user is unable to create a money request from within the chat by allowing the request to accept an account ID, so if the login is missing, the request will still succeed.

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

I tested doing money request, split, and send money and all of them can work even though the email/login is missing. We also have this PR to allow the user to do a split bill from within the chat with a user without login.

So, I believe it makes sense to show a user even without a login on the money request participant list as the BE can already handle it. We can have a new flag called includePersonalDetailsWithoutLogin and only set it to true for the money request participant list. Basically, we will have the same behavior between making a money request from FAB and from within the chat.

_.pick(personalDetails, (detail) => !includePersonalDetailsWithoutLogin && Boolean(detail.login) && !detail.isOptimisticPersonalDetail)

(or just remove the login logic for all cases)

@melvin-bot melvin-bot bot added the Overdue label Dec 25, 2023
Copy link

melvin-bot bot commented Dec 25, 2023

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

@abdulrahuman5196
Copy link
Contributor

abdulrahuman5196 commented Dec 25, 2023

Seems the issue was created near weekend. Will work on closing out review sooner.

@melvin-bot melvin-bot bot added Overdue and removed Overdue labels Dec 25, 2023
Copy link

melvin-bot bot commented Dec 29, 2023

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

Copy link

melvin-bot bot commented Dec 29, 2023

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

Copy link

melvin-bot bot commented Jan 1, 2024

@mallenexpensify, @abdulrahuman5196 Still overdue 6 days?! Let's take care of this!

@abdulrahuman5196
Copy link
Contributor

@mallenexpensify Can we retest? I don't see this issue now

@melvin-bot melvin-bot bot removed the Overdue label Jan 1, 2024
@mallenexpensify
Copy link
Contributor

I don't either, going to close. Thanks @abdulrahuman5196
image

image

@lanitochka17
Copy link

Issue is still reproducible on the latest build 1.4.28-0

20240119_222315.mp4

@lanitochka17 lanitochka17 reopened this Jan 19, 2024
Copy link

melvin-bot bot commented Jan 19, 2024

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

Copy link

melvin-bot bot commented Jan 19, 2024

@mallenexpensify @abdulrahuman5196 this issue is now 4 weeks old and preventing us from maintaining WAQ, can you:

  • Decide whether any proposals currently meet our guidelines and can be approved as-is today
  • If no proposals meet that standard, please take this issue internal and treat it as one of your highest priorities
  • If you have any questions, don't hesitate to start a discussion in #expensify-open-source

Thanks!

@mallenexpensify
Copy link
Contributor

Still on hold

@melvin-bot melvin-bot bot removed the Overdue label Feb 24, 2024
@melvin-bot melvin-bot bot added the Overdue label Mar 4, 2024
@mallenexpensify
Copy link
Contributor

@melvin-bot melvin-bot bot removed the Overdue label Mar 4, 2024
@melvin-bot melvin-bot bot added the Overdue label Mar 12, 2024
@mallenexpensify
Copy link
Contributor

@melvin-bot melvin-bot bot removed the Overdue label Mar 13, 2024
@melvin-bot melvin-bot bot added the Overdue label Mar 25, 2024
@mallenexpensify mallenexpensify added the retest-weekly Apply this label if you want this issue tested on a Weekly basis by Applause label Mar 27, 2024
@mallenexpensify mallenexpensify changed the title [HOLD #34577][$500] Request – Unable to Request money twice to the same user you have no conversation with. [$500] Request – Unable to Request money twice to the same user you have no conversation with. Mar 27, 2024
@mallenexpensify
Copy link
Contributor

Off hold, added retest-weekly

@melvin-bot melvin-bot bot removed the Overdue label Mar 27, 2024
@mallenexpensify
Copy link
Contributor

Waiting for retest, adding to #vip-split

@arielgreen arielgreen changed the title [$500] Request – Unable to Request money twice to the same user you have no conversation with. [LOW] [Splits] [$500] Request – Unable to Request money twice to the same user you have no conversation with. Apr 2, 2024
@mvtglobally
Copy link

Issue is reproducible during KI retests.

1711987915994!123321

@mvtglobally mvtglobally removed the retest-weekly Apply this label if you want this issue tested on a Weekly basis by Applause label Apr 4, 2024
@melvin-bot melvin-bot bot added the Overdue label Apr 5, 2024
@mallenexpensify mallenexpensify added the Help Wanted Apply this label when an issue is open to proposals by contributors label Apr 6, 2024
@mallenexpensify
Copy link
Contributor

Add Help Wanted label.

@melvin-bot melvin-bot bot removed the Overdue label Apr 6, 2024
Copy link

melvin-bot bot commented Apr 6, 2024

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

1 similar comment
Copy link

melvin-bot bot commented Apr 13, 2024

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

@melvin-bot melvin-bot bot added the Overdue label Apr 15, 2024
@mallenexpensify
Copy link
Contributor

Waiting for proposals.

@melvin-bot melvin-bot bot removed the Overdue label Apr 15, 2024
@lokesh-singhania
Copy link

Not able to reproduce this on Android (Chrome)

  1. Don't see Request Money option (is some setting required for it?)
  2. Tried to reproduce using Track Expense instead - but no issue found (recording below)
Screenrecorder-2024-04-19-15-42-44-209.mp4

Is this issue mac only?

Copy link

melvin-bot bot commented Apr 20, 2024

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

@mallenexpensify
Copy link
Contributor

Gonna close this, wasn't able to repro AND it's 5 months old, nav is totally different now.

2024-04-23_14-43-13.mp4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. External Added to denote the issue can be worked on by a contributor Help Wanted Apply this label when an issue is open to proposals by contributors Weekly KSv2
Projects
None yet
Development

No branches or pull requests

8 participants