[$500] IOU - It shows a location permission denied error

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

---

Version Number: 1.4.43.0
Reproducible in staging?: Y
Reproducible in production?: Y
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
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Issue found when executing PR #36147

Action Performed:

1. Start creating a distance request in a workspace chat
2. Tap on the Start
3. Tap on the "Use current location" button

Expected Result:

It should be showing my location on my map or ask for permission

Actual Result:

It shows a location permission denied error. Safari location setting can be "Ask" or "Allow"

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

Bug6385978_1708451638266.KWCX6850.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0199b0f95a9b2d0ac2
• Upwork Job ID: 1760487636301574144
• Last Price Increase: 2024-02-22

[melvin-bot]

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

[lanitochka17]

@bz 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

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~0199b0f95a9b2d0ac2

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @DylanDylann (External)

[stephanieelliott]

I think this can be external

[jeremy-croff]

It looks like it's actually default behavior to require a refresh after changing from allow to disallow or disallow to allow.. I think in this ticket the tester had it as disallow, and is not getting it to be allowed ( unless he would refresh)
I found some hacky workarounds, such as doing the location fetching in an iframe, so that it doesn't require a refresh, but this is not ideal.