Preparing for Google Play review

⚠️

The Google Play console forms mentioned below will appear only if your create a release and upload some binary to it that is eligible for those forms: targets the right SDK version and inludes the right permissions. The permissions are automatically added by HyperTrack SDK.

If you are using any release automation service like Expo EAS or Fastlane you need to do one release manually to fill the permission forms.

Get approved for the Background location access

Android 11 requires Background location access in order to start tracking when the app is in background. HyperTrack SDK declares all the required permissions in AndroidManifest.xml but you need to make some changes to your app config and description in Play Console in order to pass the Google Play Review.

Update the app description and config in Google Play Console

  • Open Play Console select your app from list
  • Scroll the left navigation bar all the way to the bottom. Then select App Content item from Policy section
  • Scroll the page down to Location permissions section
  • Click Manage to proceed
  • Fill in Policy Compliance form, focusing on user facing aspects of your app. For example HyperTrack Visits app uses following:
Input TitleSample Content
App purposeAutomate expense payouts and gather delivery sites coordinates
Location accessRequires all the time location permission to collect data of user movement for the purpose of travel expense payouts (main scenario) based on mileage driven. When the shift ends, it is possible to review the total mileage driven and which path segments contributes to the drives total (walks are not accounted in reimbursement). The latter establishes transparency that is required to trust the automation.

You need to add similar texts describing your app.

Show the explanation prompt in the app

Google Play Review requires your app to show an explanation before permission requests. In case of a Background location access the propmpt must contain the following words:
This app collects location data to ... even when the app is closed or not in use
The flow of requesting permissions should consist of two separate steps:

  1. App shows Location permission explanation prompt, containing the sentense above, and requests ACCESS_FINE_LOCATION permission.
  2. Once the previous permission is successfully granted, the app should show Background location permission prompt and request ACCESS_BACKGROUND_LOCATION permission.

Video example of proper permission experience

Check more details in official Google docs:

Submit Foreground service permissions form

Starting from Android 14 (if you have targetSDK 34+) you also need to fill in the Foreground service permissions form in order to pass the Google Play Review. This is required for apps that use foreground services for tracking or other purposes. HyperTrack SDK have to use Foreground service to track the device location in background.

You will be requested to fill the form when releasing a new version of the app. You also can find it here: Left pane > Policy and programmes > App content > Needs attention or Actioned > Foreground service permissions > Manage

To complete the form you need to select use cases that are corresponding to your app. If you start tracking session with HyperTrack using orders, you need Geofencing item. If your users manually start tracking e.g. based on shifts, you need User-initiated tracking item.

You also need to upload a video showing that feature in action. Make sure the video includes showing the Foreground service notification.

Updated about 2 months ago