Skip to content

[$500] Scan - Expense report and transaction report are no longer hidden in LHN when scanning fails #37296

Closed

Description

@kbecciv

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: v1.4.44-0
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal team

Action Performed:

  1. Go to staging.new.expensify.com.
  2. Go to workspace chat.
  3. Create a scan request with an invalid receipt that will fail the scanning.
  4. Wait for the request to fail.

Expected Result:

Workspace expense report and transaction report will be hidden in LHN when the scanning fails. (production behavior)

Actual Result:

Workspace expense report and transaction report appear in LHN when the scanning fails.

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

Bug6393871_1709032856428.bandicam_2024-02-27_11-00-21-065__1_.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~014b135358baed37a2
  • Upwork Job ID: 1762481990262865920
  • Last Price Increase: 2024-03-26
  • Automatic offers:
    • DylanDylann | Reviewer | 0
    • tienifr | Contributor | 0

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    ExternalAdded to denote the issue can be worked on by a contributor
    on Feb 27, 2024
  2. changed the title [-]Scan - Expense report and transaction report are no longer hidden in LHN when scanning fails[/-] [+][$500] Scan - Expense report and transaction report are no longer hidden in LHN when scanning fails[/+] on Feb 27, 2024
  3. melvin-bot commented on Feb 27, 2024

    @melvin-bot
  4. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Feb 27, 2024
  5. melvin-bot commented on Feb 27, 2024

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @DylanDylann (External)

  6. github-actions commented on Feb 27, 2024

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  7. kbecciv commented on Feb 27, 2024

    @kbecciv
    Author

    We think that this bug might be related to #wave5-free-submitters
    CC @dylanexpensify

  8. melvin-bot commented on Feb 27, 2024

    @melvin-bot

    Triggered auto assignment to @danieldoglas (Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  9. 56 remaining items

  10. melvin-bot commented on Apr 25, 2024

    @melvin-bot

    This issue has not been updated in over 15 days. @danieldoglas, @tienifr, @DylanDylann 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!

  11. DylanDylann commented on Apr 29, 2024

    @DylanDylann
    Contributor

    @danieldoglas Could you help to handle the payment for this issue?

  12. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on May 4, 2024
  13. melvin-bot commented on May 4, 2024

    @melvin-bot

    Triggered auto assignment to @MitchExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  14. danieldoglas commented on May 4, 2024

    @danieldoglas
    Contributor

    Sorry @DylanDylann, forgot to add the bug label. @MitchExpensify can you please help us out on paying this one? Thanks!

  15. MitchExpensify commented on May 6, 2024

    @MitchExpensify
    Contributor

    Payment summary

    C $500 @tienifr
    C+ $500 @DylanDylann

  16. MitchExpensify commented on May 6, 2024

    @MitchExpensify
    Contributor

    Paid and contract ended

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions