You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Payment due 2 March][$250] LHN - No RBR shown in LHN when amount greater than scan amount violation #75950
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:
Navigate to staging.new.expensify.com
Navigate to a workplace chat
Click on FAB -> Create expense -> Scan
Upload a digital receipt -> Wait for the smart scan to be completed
Navigate to the expense details
Click on the amount -> edit the amount to be higher than the scanned amount -> Save
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
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.
👋 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:
Identify the pull request that introduced this issue and revert it.
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
Activity
melvin-bot commentedon Nov 25, 2025
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.melvin-bot commentedon Nov 25, 2025
Triggered auto assignment to @Valforte (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Nov 25, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Nov 25, 2025
👋 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:
marcaaron commentedon Nov 25, 2025
This seems like a backend issue to me but maybe needs a frontend component. AFAICT we are not recalculating violations in Auth.
85 remaining items
Valforte commentedon Feb 6, 2026
Moving on with @daledah proposal
Valforte commentedon Feb 9, 2026
Not overdue
[-][$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[/+]laurenreidexpensify commentedon Mar 2, 2026
Payment Summary
JmillsExpensify commentedon Mar 18, 2026
$250 approved for @truph01
garrettmknight commentedon Mar 25, 2026
$250 approved for @daledah