[Distance] - Amount/Cash is not updating when editing the Merchant field

[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!

---

Issue found when executing PR #26536

Action Performed:

1. Open the staging web app
2. Click on the green + button
3. Click on Request money
4. Select Distance
5. Select a Start and Finish addresses
6. Click Next and select a Workspace
7. After request is sent, click on it to open request detail page
8. Click on the Merchant field and change the miles number of price per mile

Expected Result:

Amount/Cash field to update accordingly once Merchant or Distance field is updated

Actual Result:

Amount/Cash field does not update

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.63-0

Reproducible in staging?: Y

Reproducible in production?: Y

If this was caught during regression testing, add the test name, ID and link from TestRail:

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug6188822_Screen_Recording_2023-09-04_at_9.16.26_PM.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal team

Slack conversation:

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @kadiealexander (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[kadiealexander]

@hayata-suenaga you seem heavily involved in the linked PR, can you please take a look at this one and see if it's a bug, or maybe it's a feature request? The design doc says this about editing distance expenses:

While these fields are editable as normal, editing the amount manually will mean that the amount for payment doesn’t necessarily match the mileage receipt.

So it seems like this is expected behaviour.

[hayata-suenaga]

This is the expected behavior. Closing this