[$250] Track - Amount on the expense preview does not update when track distance expense is submitted

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.75-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: #51517
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Mac 15.0 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Distance rates are enabled.
• Workspace distance unit (miles) is different from individual distance unit (kilometers).

1. Go to staging.new.expensify.com
2. Go to self DM.
3. Track a distance expense.
4. Click Share it with my accountant.
5. Select the workspace.
6. Click Rate.
7. Select any rate.
8. Click Submit.
9. Note the amount on the expense preview in the main chat.
10. Click on the expense preview.
11. Go back to main chat.

Expected Result:

In Step 9, the amount on the expense preview should be the correct amount after the expense is created.

Actual Result:

In Step 9, the amount on the expense preview shows the old amount which is when a different rate is used in the track expense.
The amount only updates after refreshing the page (Step 11).

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6691743_1733973744772.20241212_110709.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021867155469395187403
• Upwork Job ID: 1867155469395187403
• Last Price Increase: 2024-12-12
• Automatic offers:
• paultsimura | Contributor | 105304884

Issue Owner

Current Issue Owner: @parasharrajat

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @strepanier03 (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]

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

[github-actions]

👋 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.

[IuliiaHerets]

Different behavior in production

Screen.Recording.2024-12-12.at.11.00.13.AM.mov

[Pujan92]

This is known issue and will be handled separately. Ref

cc: @paultsimura

[MariaHCD]

Thanks, @Pujan92 !

@paultsimura @neil-marcellini would you both be able to take over this issue since it is a follow up from #51517 (review)

[paultsimura]

would you both be able to take over this issue since it is a follow up from #51517 (review)

Yes, I'll start investigating the fix today.
Also IMO, it shouldn't be a blocker. This comment says the prod behavior is different, but it's only different because in prod the flow fails eventually – you can see the RBR appears after sharing the expense.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021867155469395187403

[melvin-bot]

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

[melvin-bot]

📣 @paultsimura 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖