Can't set distance rate on a new workspace, Oops... something went wrong error appears

[m-natarajan]

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: 1.4.58-2
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail: n/a
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: applause internal team
Slack conversation:

Action Performed:

1. Log in with a new expensifail account
2. Create a new workspace
3. Enable distance rates in the More features tab
4. Navigate to Distance rates
5. Tap on the distance rate
6. Tap on the rate
7. Change the rate and save it

Expected Result:

I should be able to set a new rate without errors.

Actual Result:

I can't set distance rate on a new workspace, "Oops... something went wrong" error appears when I try. Sometimes I get a Hmm... it's not here" error when trying to open the rate.

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

Add any screenshot/video evidence

Bug6433518_1711916659493.NIUY9524.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @deetergp (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.

[joekaufmanexpensify]

@deetergp do you think this should be a deploy blocker? I can reproduce

[tgolen]

I think it should, yes. This is related to the new collect workspaces being created. I'm guessing the backend is throwing an error. Can someone please get the requestID of the failed API call or at least post the login of the account you used to reproduce the issue?

[joekaufmanexpensify]

Yep, one sec!

[joekaufmanexpensify]

The account I used earlier today was jkaufman+18@expensifail.com. However, I'm trying to get a requestID for a new attempt and I can't reproduce this now on staging any longer. @tgolen are you still able to reproduce it?

[tgolen]

I wasn't able to reproduce it. You can see here that I changed the default rate to 0.672 as well as add a new rate:

[joekaufmanexpensify]

Cool. Yeah it worked for me on two different accounts just now too.

[tgolen]

I guess since neither of us can reproduce it, I'll close this for now. Thank you, Joe!

[joekaufmanexpensify]

Course!