-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[$250] Split - Chat header shows split creator and split user avatar briefly when splitting expense #40904
Comments
Triggered auto assignment to @anmurali ( |
@anmurali FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
We think that this bug might be related to #vip-split |
ProposalPlease re-state the problem that we are trying to solve in this issue.The report header avatar shows both user avatars when doing a split bill with a new user. What is the root cause of that problem?The avatar will show all participant avatars in a report. Line 1942 in b0ec7b1
When we create a new split with a new user, we optimistically create a new chat with a participant that contains both users. Line 3104 in b0ec7b1
Lines 3123 to 3124 in b0ec7b1
But if it's a DM, the participant will exclude the current user, so when the request is completed, BE returns the correct participant, and the correct avatar is shown. What changes do you think we should make in order to solve the problem?For DM case, we should set the participant without the current user, Lines 3123 to 3124 in b0ec7b1
|
@anmurali Eep! 4 days overdue now. Issues have feelings too... |
Job added to Upwork: https://www.upwork.com/jobs/~019386f7d8c4cc34c1 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Pujan92 ( |
@bernhardoj's proposal looks good which is suggested to pass 🎀👀🎀 C+ reviewed |
Triggered auto assignment to @madmax330, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@madmax330 do you agree with this? Can I assign the issue to @bernhardoj |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@madmax330 @anmurali @Pujan92 this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
📣 @Pujan92 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @bernhardoj 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
PR is ready cc: @Pujan92 |
This issue has not been updated in over 15 days. @madmax330, @anmurali, @Pujan92, @bernhardoj eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
The PR is merged. I think it's ready for payment @anmurali. |
Bump @anmurali for the payment! |
Paid everyone. |
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: 1.4.65-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
The chat header will show the split user avatar
Actual Result:
The chat header shows split creator and split user avatar briefly.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6460097_1713955443502.20240424_183933.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: