Skip to content

[RCA #72674] Expense - Amount is blank, Distance field is Pending when distance expense amount is 0 #75388

Closed as not planned

Description

@jponikarchuk

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.2.60-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #72674
Email or phone of affected tester (no customers): sjdsjnodijsisjio@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

  • Have a working self DM.
  1. Go to staging.new.expensify.com
  2. Go to self DM.
  3. Click + > Track distance > Manual.
  4. Enter 0 > Next.
  5. Click Create expense.
  6. Open transaction thread.

Expected Result:

Amount will show 0.00. Distance field will show the correct amount.

Actual Result:

Amount is blank, Distance field is Pending when distance expense amount is 0.

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

1.mp4

View all open jobs on GitHub

Activity

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

    @melvin-bot

    Triggered auto assignment to @bfitzexpensify (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 18, 2025

    @melvin-bot

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

  4. github-actions commented on Nov 18, 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.
  5. melvin-bot commented on Nov 18, 2025

    @melvin-bot

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

  6. Valforte commented on Nov 18, 2025

    @Valforte
    Contributor

    @Gonals looks like a regression from your #72674 PR. Should we revert here?

  7. Gonals commented on Nov 18, 2025

    @Gonals
    Contributor

    If we can avoid reverting that monster, I would be way happier. Let me take a look and see if we can CP a fix

  8. changed the title [-]Expense - Amount is blank, Distance field is Pending when distance expense amount is 0[/-] [+][RCA #72674] Expense - Amount is blank, Distance field is Pending when distance expense amount is 0[/+] on Nov 18, 2025
  9. melvin-bot commented on Nov 18, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  10. melvin-bot commented on Nov 18, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  11. melvin-bot commented on Nov 19, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  12. IuliiaHerets commented on Nov 19, 2025

    @IuliiaHerets

    Issue can't be reproduced anymore in the latest build

    20251119_162923.mp4
  13. grgia commented on Nov 19, 2025

    @grgia
    Contributor

    Thank you for retesting @IuliiaHerets !

  14. reopened this on Nov 19, 2025
  15. Gonals commented on Nov 19, 2025

    @Gonals
    Contributor

    Reopening, as this had a backend fix in place that we still want to merge

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.EngineeringHourlyKSv2ReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions