Workspace - 'Track distance' has rate = 0 and endless spinner is shown instead of block ‘Unlock next-day reimbursements’

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

---

Action Performed:

1. Create and verify NEW expensifail account
2. Create NEW workspace
3. Goto Workspace > Reimbursements
4. Check 'Track distance' rate
5. Log out from account and login again

Expected Result:

'Track distance' has default rate
Workspace is saved in the account after relogin

Actual Result:

'Track distance' has rate = 0. Endless spinner is shown instead of block ‘Unlock next-day reimbursements’
Workspace is NOT saved in the account after re-login

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

Reproducible in staging?: Yes

Reproducible in production?: No

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

Bug6097120_WS-Web-reimbursements-0rate-endless-spinner.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[OSBotify]

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

[melvin-bot]

Triggered auto assignment to @thienlnam (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[luacmartins]

I'm not able to reproduce this.

[luacmartins]

nvm, this does happen for a brand new account.

[marcochavezf]

I see the Concierge chat is not loading, probably it's a side-effect of #21036 (comment)

[luacmartins]

Coming from this thread, this seems to be caused by #fireroom-getpersonaldetailslist. Gonna remove the deploy blocker label and add a hold to retest once Auth is deployed.