-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[$500] mWeb - IOU - "1 in scanning" message still shows after a failed scan #33504
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01c715ca23261fdd10 |
Triggered auto assignment to @kevinksullivan ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @fedirjh ( |
Same root cause as #33550 |
@kevinksullivan, @fedirjh Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@kevinksullivan lets put it on hold for #33550. |
@kevinksullivan, @fedirjh Huh... This is 4 days overdue. Who can take care of this? |
Issue not reproducible during KI retests. (First week) |
@kevinksullivan, @fedirjh Still overdue 6 days?! Let's take care of this! |
@kevinksullivan @fedirjh 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! |
@kevinksullivan, @fedirjh 10 days overdue. I'm getting more depressed than Marvin. |
I couldn’t reproduce, I guess we can close it. CleanShot.2024-01-09.at.13.40.54.mp4 |
Issue not reproducible during KI retests. (Second week) |
@kevinksullivan @fedirjh this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks! |
@kevinksullivan, @fedirjh Whoops! This issue is 2 days overdue. Let's get this updated quick! |
cc @kevinksullivan let's close this one. |
@kevinksullivan, @fedirjh Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@kevinksullivan, @fedirjh Huh... This is 4 days overdue. Who can take care of this? |
Issue not reproducible during KI retests. (Third week) |
@kevinksullivan @fedirjh this issue is now 4 weeks old and preventing us from maintaining WAQ, can you:
Thanks! |
Job added to Upwork: https://www.upwork.com/jobs/~0151e2987d6b5ce23e |
Current assignee @fedirjh is eligible for the Internal assigner, not assigning anyone new. |
Awaiting final action from @kevinksullivan, bug was already fixed. |
My bad missed this one @fedirjh |
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: 1.4.16-3
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:
Action Performed:
Navigate to https://staging.new.expensify.com/
Navigate to a workspace chat where an IOU was sent already
Start making a "Scan" IOU that'll fail
Wait for the scan to fail
Navigate back to the workspace chat
Expected Result:
The message should disappear
Actual Result:
"1 in scanning" message still shows after a failed scan
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6324049_1703255185184.NURJ7353.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: