[android] Google Play has rejected an update because of FOREGROUND_SERVICE usage #10140

New issue

Closed

opened 2025-01-27 09:36:08 +00:00 by rtsisyk · 0 comments

rtsisyk commented

2025-01-27 09:36:08 +00:00

Owner

Hi Developers at Organic Maps,

After a recent review, we found that your app Organic Maps: Hike Bike Drive (app.organicmaps) is not compliant with one or more of our Developer Program Policies. See below for more information about your app's status and how to correct the issue.
Publishing Status
App Status: Rejected

Your app has been rejected and wasn't published due to the policy issue(s) listed below. If you submitted an update, the previous version of your app is still available on Google Play.

Issue found: Play Console declaration and/or app description in Google Play Store does not sufficiently demonstrate the use of permission.

We are unable to approve your app’s use of FOREGROUND_SERVICE permission because we found the following information provided to be insufficient in evaluating compliance with foreground service permission requirements:

The video link you provided in the Play Console declaration and/or
The app description in the Google Play store.

Issue details

We found an issue in the following area(s):

Version code 24112712

Version code 25012609

To bring your app into compliance, follow these steps:

Please verify that the version of the app submitted for review is working as intended and that the app description on the Google Play Store accurately reflects the core functionality that requires the use of [foreground service permission](https://developer.android.com/about/versions/14/changes/fgs-types-required).
Submit an updated declaration with clear and relevant video demonstrating the core feature’s dependency on the foreground service permission.
Make any necessary corrections or modifications to meet the policy requirement.
Ensure valid testing credentials are provided.

About the Permissions for Foreground Services

The Foreground Service permission ensures the appropriate use of user-facing foreground services. For apps targeting Android 14 and above, you must specify a valid foreground service type for each foreground service used in your app, and declare the foreground service permission that is appropriate for that type. For example, if your app’s use case requires map geolocation, you must declare the FOREGROUND_SERVICE_LOCATION permission in your app’s manifest.
With the exceptions of systemExempted and shortService foreground service types, apps are only allowed to declare a foreground service permission if the use:

Provides a feature that is beneficial to the user and relevant to the core functionality of the app.
Is initiated by the user or is user perceptible (for example, audio from playing a song, cast media to another device, accurate and clear user notification, user request to upload a photo to the cloud).
Can be terminated or stopped by the user.
Can’t be interrupted or deferred by the system without causing a negative user experience or causing the user anticipated feature to not work as intended (for example, a phone call needs to start immediately and can’t be deferred by the system).
Runs only for as long as necessary to complete the task.

The use of foreground service is further explained on this Play Console Help Center page.
Action required: Submit an updated app for review
Here's what to do to help get your app on Google Play:

Make sure to read the applicable policies or requirements listed below:
    [Permissions for Foreground Services](https://support.google.com/googleplay/android-developer/answer/9888379?sjid=2204047796652818743-NA&visit_id=638735671984464297-2232262365&rd=1)
Make appropriate changes to your app (if possible), and be sure to address the issue described above. You may also want to check your app's store listing for compliance, if applicable.
Double check that your app is compliant with all other [Developer Program Policies](https://play.google/developer-content-policy/).

Hi Developers at Organic Maps, After a recent review, we found that your app Organic Maps: Hike Bike Drive (app.organicmaps) is not compliant with one or more of our Developer Program Policies. See below for more information about your app's status and how to correct the issue. Publishing Status App Status: Rejected Your app has been rejected and wasn't published due to the policy issue(s) listed below. If you submitted an update, the previous version of your app is still available on Google Play. Issue found: Play Console declaration and/or app description in Google Play Store does not sufficiently demonstrate the use of permission. We are unable to approve your app’s use of [FOREGROUND_SERVICE](https://developer.android.com/reference/android/Manifest.permission#FOREGROUND_SERVICE) permission because we found the following information provided to be insufficient in evaluating compliance with [foreground service permission requirements](https://support.google.com/googleplay/android-developer/answer/13392821?hl=en&sjid=5928478178588015754-NA): The video link you provided in the Play Console declaration and/or The app description in the Google Play store. Issue details We found an issue in the following area(s): Version code 24112712 Version code 25012609 To bring your app into compliance, follow these steps: Please verify that the version of the app submitted for review is working as intended and that the app description on the Google Play Store accurately reflects the core functionality that requires the use of [foreground service permission](https://developer.android.com/about/versions/14/changes/fgs-types-required). Submit an updated declaration with clear and relevant video demonstrating the core feature’s dependency on the foreground service permission. Make any necessary corrections or modifications to meet the policy requirement. Ensure valid testing credentials are provided. About the [Permissions for Foreground Services](https://support.google.com/googleplay/android-developer/answer/9888379?sjid=2204047796652818743-NA&visit_id=638735671984464297-2232262365&rd=1) The Foreground Service permission ensures the appropriate use of user-facing foreground services. For apps targeting Android 14 and above, you must specify a valid foreground service type for each foreground service used in your app, and declare the foreground service permission that is appropriate for that type. For example, if your app’s use case requires map geolocation, you must declare the FOREGROUND_SERVICE_LOCATION permission in your app’s manifest. With the exceptions of systemExempted and shortService foreground service types, apps are only allowed to declare a foreground service permission if the use: Provides a feature that is beneficial to the user and relevant to the core functionality of the app. Is initiated by the user or is user perceptible (for example, audio from playing a song, cast media to another device, accurate and clear user notification, user request to upload a photo to the cloud). Can be terminated or stopped by the user. Can’t be interrupted or deferred by the system without causing a negative user experience or causing the user anticipated feature to not work as intended (for example, a phone call needs to start immediately and can’t be deferred by the system). Runs only for as long as necessary to complete the task. The use of foreground service is further explained on this [Play Console Help Center](https://support.google.com/googleplay/android-developer/answer/9888379?sjid=2204047796652818743-NA&visit_id=638735671984464297-2232262365&rd=1) page. Action required: Submit an updated app for review Here's what to do to help get your app on Google Play: Make sure to read the applicable policies or requirements listed below: [Permissions for Foreground Services](https://support.google.com/googleplay/android-developer/answer/9888379?sjid=2204047796652818743-NA&visit_id=638735671984464297-2232262365&rd=1) Make appropriate changes to your app (if possible), and be sure to address the issue described above. You may also want to check your app's store listing for compliance, if applicable. Double check that your app is compliant with all other [Developer Program Policies](https://play.google/developer-content-policy/).

This repo is archived. You cannot comment on issues.