Desktop - IOU - The Distance IOU is unable to determine the user's coordinates

[kbecciv]

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.56-0
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4446001
Issue reported by: Applause - Internal team

Action Performed:

1. Open NewDot app
2. Log in to the employee account
3. Navigate to the WS room
4. Navigate to Request money -> Distance -> Start
5. In the Address field, select the "Use current location" option

Expected Result:

When using the "Use current location" option in the Distance IOU, the application must determine the user's coordinates.

Actual Result:

The Distance IOU is unable to determine the user's coordinates.

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

Bug6424107_1711180240019.Recording__1464.mp4

View all open jobs on GitHub

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

[melvin-bot]

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

[kbecciv]

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

[roryabraham]

not able to reproduce on dev on main. I suspect this may be a back-end issue

[roryabraham]

not able to reproduce this on staging web either, though I just noticed this was reported on desktop. I'll check there...

[roryabraham]

I got this error on desktop:

the link just links to Expensify Help and not a specific page, which isn't very helpful

[roryabraham]

This may be a regression from #38442

[roryabraham]

seeing the same error locally

[hayata-suenaga]

seeing the same error locally

If you haven't manually added the GCP key in your local .env, then it's expected that the current location feature won't work on the local desktop app because of the changes I made

[hayata-suenaga]

but this shouldn't happen on the staging or production. I'll also gonna investigate it