Closed kavimuru closed 1 year ago
Triggered auto assignment to @conorpendergrast (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details.
Platforms
in OP are ✅)conorpendergrast+19981c@gmail.com created the split, then changed the default contact method to conorpendergrast+19981cc@gmail.com
Before the default contact method change:
After the default contact method change:
Job added to Upwork: https://www.upwork.com/jobs/~01b4c1bac53442a0dd
Current assignee @conorpendergrast is eligible for the External assigner, not assigning anyone new.
Triggered auto assignment to Contributor-plus team member for initial proposal review - @thesahindia (External
)
Triggered auto assignment to @madmax330 (External
), see https://stackoverflow.com/c/expensify/questions/7972 for more details.
Primary login account A is added to the split bill participant list, amount is also divided between primary login account and secondary login account on changing default contact method.
There're 3 user A, B, C. User A has another contact method AA.
A splits bill between A, B and C. then A changes contact method to AA.
Let's see this line https://github.com/Expensify/App/blob/af6fb0768b65e95f8a9feb5e36626ae9df5f2097/src/pages/iou/SplitBillDetailsPage.js#L70
The participants
are [AA, B, C] (Since A already changes contact to AA). The reportAction.actorEmail
is A (it's the original login). So in this line, it should have filtered AA
out so we have the list of participants "without payee", but in this case it doesn't since the login in participants
is the new contact method, while the actorEmail
is the old method.
So we'll see the payee duplicate in the list of Who was there?
.
We need to change how we compare 2 participants/actors are the same
. Currently we're comparing emails but they can change if anyone changes their contact method. So we need to:
accountID
I believe there's back-end change required to save the accountID
of the actor
as well as some changes to save it along with the participants list when splitting bill.
We can also get the list of contact methods of both sides (by their current contact method) and check if there's any contact method in common. For this we need to change the personalDetails
structure to include the loginList
for all people as well, then get it to compare whenever we need to check if both emails are of the same person.
The primary login account is added to the split bill participant list and the amount also gets divided changing the default contact method
reportAction.originalMessage.participants
not updated to the recent default contact method.
We started to use participants data here: https://github.com/Expensify/App/blob/0813e2ca1476635a8324cbd9f998424663a33128/src/pages/iou/SplitBillDetailsPage.js#L67
That makes users' old default contact added to split participants.
Update the originalMessage participants to the current default contact method in the backend.
N/A
@thesahindia have you had a chance to review the proposals?
@madmax330, looked into the proposal and look like this needs backend changes.
Okay will ask internally to see if anyone knows about this.
@tienifr I think using the accountId makes sense and we are actively working now to make sure we are re-keying the personal details with accountIDs so I believe this should work well
📣 @tienifr You have been assigned to this job by @madmax330! Please apply to this job in Upwork and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻 Keep in mind: Code of Conduct | Contributing 📖
Actually we discussed this internally and we're refactoring personalDetails by accountID already. So let's hold on that so that we don't duplicate work
Still on hold for https://github.com/Expensify/App/issues/19007
@madmax330 I see that https://github.com/Expensify/App/issues/19007 is now on Production, so I think we can take this off hold, re-test and fix. Do you agree?
Yeah seems like we can take this off hold
Off-hold, ready to re-test and fix (if it still exists as an issue)
I cannot reproduce this bug now. I found out that this issue was fixed in the PR https://github.com/Expensify/App/pull/20328 and the related issue https://github.com/Expensify/App/issues/19007 where we migrated login to accountID
through the app, which was the approach mentioned in my proposal.
Just wonder if I'm eligible for a bonus here? @conorpendergrast
Removing from the manual request project since this is a wave2 issue.
@tienifr What are you asking for as compensation? We can certainly discuss it!
Ok, I agree with that! I'll queue up contracts via Upwork.com now (the job post is closed so I need to do that manually)
Original Upwork job: https://www.upwork.com/jobs/~01b4c1bac53442a0dd
Accepted the offer. Thanks @conorpendergrast
Paid @tienifr 👍 Closing, as @thesahindia will send a Manual Request.
$1,000 payment approved for @thesahindia based on BZ summary.
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Precondition: account should have primary login account A, and secondary login account B
Expected Result:
Primary login account A shouldn't be added to the split bill participant list
Actual Result:
Primary login account A is added to the split bill participant list amount is also divided between primary login account and secondary login account on changing default contact method.
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?
Version Number: 1.3.22 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
https://github.com/Expensify/App/assets/43996225/66585e83-865d-4891-93b0-b98950edfe32
https://github.com/Expensify/App/assets/43996225/165d8a92-0bfb-4fb0-8ef9-ffb955d46e55
Expensify/Expensify Issue URL: Issue reported by: @natnael-guchima Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1685434411591889 https://expensify.slack.com/archives/C049HHMV9SM/p1685430101536709 View all open jobs on GitHub
Upwork Automation - Do Not Edit