-
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
[HOLD for payment 2024-05-22] [$250] mWeb - In room,inviting an user& creating split scan not displaying Scan in progress in lhn #40557
Comments
Triggered auto assignment to @zanyrenney ( |
@zanyrenney 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. |
This bug might be related to #vip-vsb |
ProposalPlease re-state the problem that we are trying to solve in this issue.When doing a split bill scan in a room, the LHN last message doesn't show Scan in progress. If we do this in, let say a group chat, the LHN last message will show Scan in progress. What is the root cause of that problem?If it's a chat room, the last message value will be based on the report Lines 321 to 363 in 8616678
The last action is taken from Lines 35 to 47 in 8616678
Notice that in the filter, we filter out any whisper action, which is true for scan requests while scanning. So, the scan request is never taken into consideration and the last message will be the previous message. But as I mentioned in the first section above, this doesn't happen when we do the split bill scan in a group chat for example. That's because, for group chat, we get the last message from Lines 390 to 393 in 8616678
and Lines 316 to 319 in 8616678
In App/src/libs/OptionsListUtils.ts Lines 568 to 569 in 8616678
In App/src/libs/ReportActionsUtils.ts Line 567 in 8616678
That's why the split bill scan request is taken into consideration as the last action. What changes do you think we should make in order to solve the problem?We should make the last action logic consistent for the last message text. In SidebarUtils itself, we have 3 ways to get the last action. One is the last action that doesn't get through the filter, two get through the filter (one filter with App/src/libs/OptionsListUtils.ts Lines 570 to 571 in 8616678
App/src/libs/OptionsListUtils.ts Line 569 in 8616678
App/src/libs/OptionsListUtils.ts Lines 265 to 272 in 8616678
App/src/libs/OptionsListUtils.ts Line 724 in 8616678
Here is the plan:
NOTE: |
Agree, this looks related to VIP VSB |
Job added to Upwork: https://www.upwork.com/jobs/~0169b520297273f864 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @thesahindia ( |
Already have a proposal above! @thesahindia please take a look and let me know if we can hire @bernhardoj |
bump @thesahindia if you don't have capacity to review the proposal, please let me know and I will assign another C+ |
@bernhardoj's proposal looks good to me! 🎀 👀 🎀 C+ reviewed |
Triggered auto assignment to @yuwenmemon, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
📣 @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: @thesahindia |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
The PR is reverted because of a regression. The new PR is ready cc: @thesahindia |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.73-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-05-22. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@thesahindia please complete the checklist above before I can issue payment. Thanks! |
We were filtering out all whisper actions, which caused this. Test case steps -
|
payment summary paid $250 to @bernhardoj via UW. Closing! |
$250 approved for @thesahindia |
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.63-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: EXP around https://expensify.testrail.io/index.php?/tests/view/4495609
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:
Go to https://staging.new.expensify.com/
Tap fab -- start chat -- room
Create a room
4.Tap header---members and invite a member
5.Navigate back to room page
6.Tap plus--- split expense-- scan
7.Upload an image using camera
8.Tap split expense
9.Note scan in progress shown in preview
10.Open the expense and note header message shown scanning
11.Navigate to LHN
Expected Result:
In room, after inviting an user& creating split scan expense must display Scan in progress message in lhn.
Actual Result:
In room, after inviting an user& creating split scan expense displays invited 1user message in LHN instead of Scan in progress message.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6454325_1713479892547.rov.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @zanyrenneyThe text was updated successfully, but these errors were encountered: