[P2P Distance] - Error shows up after selecting distance rate without tax rate and tax reclaimable

[IuliiaHerets]

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: v9.0.17-1

Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): applausetester+kh050806@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

Precondition:

• Track tax is enabled on Workspace settings > Distance rates > Settings.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Distance rates.
3. Create a distance rate.
4. Do not assign a tax rate and tax reclaimable to the distance rate.
5. Go to workspace chat.
6. Submit a distance expense with distance rate different from the rate created in Step 4.
7. Go to transaction thread.
8. Click Rate.
9. Select the distance rate without tax rate from Step 4.

Expected Result:

User will be able to select the distance rate without tax rate and tax reclaimable.

Actual Result:

Error shows up after selecting the distance rate without tax rate and tax reclaimable.

Workaround:

Unknown

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6564262_1723025936008.20240807_181156.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @Christinadobrzyn

[melvin-bot]

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]

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

[IuliiaHerets]

We think that this bug might be related to #wave-collect - Release 2

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

[trjExpensify]

The Rate field is not on staging for me in my tom@trj.chat account, because it's a feature behind the p2pDistanceRequests beta and that account isn't on the beta.

So I think this can be demoted as a deploy blocker.