[$500] Android - Distance - No location access prompt after relaunching app when "Only this time" is chosen

[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.15-4
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:

Isue found when excuting PR #33157

Action Performed:

1. . Tap + > Request money
2. Go to Distance
3. Select "Only this time" for location access
4. Kill app
5. Relaunch the app
6. Tap + > Request money
7. Go to Distance

Expected Result:

App will ask for location access again after killing the app because "Only this time" for location access was selected

Actual Result:

App does not ask for location access after killing the app

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

Bug6322746_1703167139619.Screen_Recording_20231221_204426_New_Expensify.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~015a8185bc88c68849
• Upwork Job ID: 1737842173239119872
• Last Price Increase: 2023-12-28

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~015a8185bc88c68849

[melvin-bot]

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

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[melvin-bot]

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

[bernhardoj]

Looks like it's expected if you reopen the app a short time after closing the app https://stackoverflow.com/questions/64464661/android-11-only-this-time-permission-behavior

[ikevin127]

TLDR:

Android allows 1 minute from the moment the app goes into the background or is killed until the one-time permission is revoked.

The Android one-time permission documentation says:

If the user sends your app to the background, your app can continue to access the data for a short period of time.

From the Android source code we can see this "short period of time" is exactly 1 minute:

/**
 * The default length of the timeout for one-time permissions
 */
public static final long ONE_TIME_PERMISSIONS_TIMEOUT_MILLIS = 1 * 60 * 1000; // <- 1 minute

/**
 * The default length to wait before ending a one-time permission session after all processes
 * are dead.
 */
public static final long ONE_TIME_PERMISSIONS_KILLED_DELAY_MILLIS = 5 * 1000;

[melvin-bot]

@laurenreidexpensify, @situchan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!