[HOLD for payment 2024-05-02] Distance - Selected distance rate is not highlighted in rate list

[kbecciv]

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: 1.4.64-0
Reproducible in staging?: y
Reproducible in production?: n
Issue found when executing PR: #38543
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Go to + > Submit expense > Distance.
4. Proceed to confirmation page.
5. Click Rate below Distance.

Expected Result:

The selected distance rate will be highlighted.

Actual Result:

The selected distance rate is not highlighted.

Workaround:

n/a

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

Add any screenshot/video evidence

Bug6457635_1713803228909.bandicam_2024-04-23_00-24-38-069.mp4

View all open jobs on GitHub

[melvin-bot]

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

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

[kbecciv]

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

[mountiny]

cc @neil-marcellini @koko57

[mountiny]

This is minor so demoting, the checkmark is there

[koko57]

@mountiny please assign this one to me

[koko57]

@mountiny fixed, adding this to the follow up PR

cc: @neil-marcellini

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.65-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Feat/36985 create new rate field followups #40711

If no regressions arise, payment will be issued on 2024-05-02. 🎊

For reference, here are some details about the assignees on this issue:

• @koko57 does not require payment (Contractor)

[melvin-bot]

Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.

[melvin-bot]

@yuwenmemon, @koko57 Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

@yuwenmemon, @koko57 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[mountiny]

I believe this can be closed