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

[$500] mWeb - IOU - "1 in scanning" message still shows after a failed scan #33504

Closed
1 of 6 tasks
lanitochka17 opened this issue Dec 22, 2023 · 25 comments
Closed
1 of 6 tasks
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Engineering Internal Requires API changes or must be handled by Expensify staff

Comments

@lanitochka17
Copy link

lanitochka17 commented Dec 22, 2023

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:

  1. Navigate to https://staging.new.expensify.com/

  2. Navigate to a workspace chat where an IOU was sent already

  3. Start making a "Scan" IOU that'll fail

  4. Wait for the scan to fail

  5. 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?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6324049_1703255185184.NURJ7353.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0151e2987d6b5ce23e
  • Upwork Job ID: 1748390765087760384
  • Last Price Increase: 2024-01-19
@lanitochka17 lanitochka17 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 mWeb - IOU - "1 in scanning" message still shows after a failed scan [$500] mWeb - IOU - "1 in scanning" message still shows after a failed scan Dec 22, 2023
Copy link

melvin-bot bot commented Dec 22, 2023

Job added to Upwork: https://www.upwork.com/jobs/~01c715ca23261fdd10

Copy link

melvin-bot bot commented Dec 22, 2023

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

@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

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 - @fedirjh (External)

@bernhardoj
Copy link
Contributor

Same root cause as #33550

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

melvin-bot bot commented Dec 26, 2023

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

@fedirjh
Copy link
Contributor

fedirjh commented Dec 28, 2023

@kevinksullivan lets put it on hold for #33550.

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

melvin-bot bot commented Jan 2, 2024

@kevinksullivan, @fedirjh Huh... This is 4 days overdue. Who can take care of this?

@mvtglobally
Copy link

Issue not reproducible during KI retests. (First week)

Copy link

melvin-bot bot commented Jan 4, 2024

@kevinksullivan, @fedirjh Still overdue 6 days?! Let's take care of this!

Copy link

melvin-bot bot commented Jan 5, 2024

@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!

Copy link

melvin-bot bot commented Jan 8, 2024

@kevinksullivan, @fedirjh 10 days overdue. I'm getting more depressed than Marvin.

@fedirjh
Copy link
Contributor

fedirjh commented Jan 9, 2024

I couldn’t reproduce, I guess we can close it.

CleanShot.2024-01-09.at.13.40.54.mp4

@melvin-bot melvin-bot bot removed the Overdue label Jan 9, 2024
@mvtglobally
Copy link

Issue not reproducible during KI retests. (Second week)

@melvin-bot melvin-bot bot added the Overdue label Jan 11, 2024
Copy link

melvin-bot bot commented Jan 12, 2024

@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!

Copy link

melvin-bot bot commented Jan 12, 2024

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

@fedirjh
Copy link
Contributor

fedirjh commented Jan 12, 2024

cc @kevinksullivan let's close this one.

@melvin-bot melvin-bot bot added Overdue and removed Overdue labels Jan 12, 2024
Copy link

melvin-bot bot commented Jan 16, 2024

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

Copy link

melvin-bot bot commented Jan 18, 2024

@kevinksullivan, @fedirjh Huh... This is 4 days overdue. Who can take care of this?

@mvtglobally
Copy link

Issue not reproducible during KI retests. (Third week)

Copy link

melvin-bot bot commented Jan 19, 2024

@kevinksullivan @fedirjh 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!

@melvin-bot melvin-bot bot added Internal Requires API changes or must be handled by Expensify staff and removed 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 labels Jan 19, 2024
Copy link

melvin-bot bot commented Jan 19, 2024

Job added to Upwork: https://www.upwork.com/jobs/~0151e2987d6b5ce23e

Copy link

melvin-bot bot commented Jan 19, 2024

Current assignee @fedirjh is eligible for the Internal assigner, not assigning anyone new.

@fedirjh
Copy link
Contributor

fedirjh commented Jan 22, 2024

Awaiting final action from @kevinksullivan, bug was already fixed.

@kevinksullivan
Copy link
Contributor

My bad missed this one @fedirjh

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. Daily KSv2 Engineering Internal Requires API changes or must be handled by Expensify staff
Projects
None yet
Development

No branches or pull requests

5 participants