Skip to content

Expense - Incorrect LHN preview after changing expense details #64654

Closed

Description

@lanitochka17

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: 9.1.70-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): sdjoinjsddoisjio@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Open 1:1 DM with user that has no unsettled expense
  3. Submit an expense to the user
  4. Open the expense report
  5. Click Amount
  6. Edit the amount and save it

Expected Result:

LHN preview will show "changed the amount to x"

Actual Result:

LHN preview shows "You modified expense ". New amount i..."

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6865488_1750428488561.20250620_220613.mp4

View all open jobs on GitHub

Activity

  1. melvin-bot commented on Jun 20, 2025

    @melvin-bot

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

  2. github-actions commented on Jun 20, 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.
  3. melvin-bot commented on Jun 20, 2025

    @melvin-bot

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

  4. thelullabyy commented on Jun 20, 2025

    @thelullabyy
    Contributor

    @NikkiWines It comes from my PR, please help to merge the revert PR and CP it

  5. NikkiWines commented on Jun 20, 2025

    @NikkiWines
    Contributor

    @lanitochka17 can we get a re-test of this please? It should be fixed 🙇

  6. NikkiWines commented on Jun 21, 2025

    @NikkiWines
    Contributor

    No longer reproducible

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions