Skip to content

[Payment due 2 March][$250] LHN - No RBR shown in LHN when amount greater than scan amount violation #75950

Closed

Description

@mitarachim

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: v9.2.62-5
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://github.com/Expensify/Expensify/issues/496911
Email or phone of affected tester (no customers): testpayment935@gmail.com
Issue reported by: Applause Internal Team
Device used: Mweb
App Component: Left Hand Navigation (LHN)

Action Performed:

  1. Navigate to staging.new.expensify.com
  2. Navigate to a workplace chat
  3. Click on FAB -> Create expense -> Scan
  4. Upload a digital receipt -> Wait for the smart scan to be completed
  5. Navigate to the expense details
  6. Click on the amount -> edit the amount to be higher than the scanned amount -> Save
  7. Note that after a while a violation is displayed indicating the amount is higher than the scanned receipt and GBR remains shown in LHN for Workspace chat
  8. Submit the expense.

Expected Result:

RBR is shown in LHN for Workspace chat after submitting the expense

Actual Result:

No GBR is shown in LHN. GBR persist in the workspace chat LHN.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug7012585_1764027113137.Screen_Recording_20251125_022251_Chrome.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021995536780251548324
  • Upwork Job ID: 1995536780251548324
  • Last Price Increase: 2026-02-04
Issue OwnerCurrent Issue Owner: @

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Nov 25, 2025
  2. melvin-bot commented on Nov 25, 2025

    @melvin-bot

    Triggered auto assignment to @Christinadobrzyn (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.

  3. melvin-bot commented on Nov 25, 2025

    @melvin-bot

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

  4. melvin-bot commented on Nov 25, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Nov 25, 2025

    @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.
  6. marcaaron commented on Nov 25, 2025

    @marcaaron
    Contributor

    This seems like a backend issue to me but maybe needs a frontend component. AFAICT we are not recalculating violations in Auth.

  7. 85 remaining items

  8. Valforte commented on Feb 6, 2026

    @Valforte
    Contributor

    Moving on with @daledah proposal

  9. added and removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Feb 6, 2026
  10. Valforte commented on Feb 9, 2026

    @Valforte
    Contributor

    Not overdue

  11. changed the title [-][$250] LHN - No RBR shown in LHN when amount greater than scan amount violation[/-] [+][Payment due 2 March][$250] LHN - No RBR shown in LHN when amount greater than scan amount violation[/+] on Feb 26, 2026
  12. laurenreidexpensify commented on Mar 2, 2026

    @laurenreidexpensify
    Contributor

    Payment Summary

    • @truph01 can request $250 in New Expensify
    • @daledah can request $250 in New Expensify
  13. JmillsExpensify commented on Mar 18, 2026

    @JmillsExpensify
    Contributor

    $250 approved for @truph01

  14. garrettmknight commented on Mar 25, 2026

    @garrettmknight
    Contributor

    $250 approved for @daledah

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.EngineeringExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions