[HOLD for payment 2024-07-10] [$250] Distance - Blue dot does not set to current location after enabling location access

[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.79-6
Reproducible in staging?: y
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4597262
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:

precondition: location access is disabled

1. Open the app and log in
2. Tap the FAB > Submit expense >Distance
3. Select do not allow on the pop-up and wait for the map to load
4. Tap the start point and select Use current location
5. Allow location access

Expected Result:

The blue dot is displayed as user's current location and replaces the start point on the map

Actual Result:

The blue dot is still displayed over San Francisco while the start point is set to the current location

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

Bug6502239_1717554700706.video_2024-06-04_22-29-07.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0194e3d6c394ce03d6
• Upwork Job ID: 1798364343763573802
• Last Price Increase: 2024-06-12
• Automatic offers:
• fedirjh | Reviewer | 102783101
• ZhenjaHorbach | Contributor | 102783102

Issue Owner

Current Issue Owner: @sakluger

[melvin-bot]

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

[m-natarajan]

@dangrous FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[m-natarajan]

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

[dangrous]

Yep, this seems like it should be external! I'll try to look into it to but open to proposals. I didn't see an obvious PR that would have caused it but will investigate.

@m-natarajan this doesn't happen on production, correct?