hola, saben por que me rechazo en playstore? me llego este correo
pp 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: Service interruption or deferment of functionality does not have material user impact
We found that one or more of the declared use cases is not compliant with how foreground service permission is allowed to be used. Specifically, the declared use case(s) can be interrupted or deferred by the system without creating a negative user experience. Your app is using foreground service to Health - Other when it is not required to do so.
Issue details
We found an issue in the following area(s):
- Version code 100000072
To bring your app into compliance, follow these steps :
Please remove the use of foreground service from the impacted use case(s) in your app and consider migration to alternative APIs such as WorkManager.
If required, remove the applicable foreground service type permission from all version codes within the submission. This includes both production and testing tracks.
To make APK/App bundle-level updates, follow these steps:
- Go to App bundle explorer and search for the noncompliant version codes. Click on the details page to navigate to the track(s) with the policy issue (Closed / Open testing / Production). Click Manage track > Create new release.
- If the release with the violating app bundles/APKs are in a draft state, discard the release.
- Otherwise, add the policy-compliant version of app bundles/APKs.
- Make sure that the noncompliant version is under the “Not included” section of this release.
- Enter a release name and click Save. Once saved, click Review release, and then proceed to roll out the release to 100% and completely deactivate the noncompliant APK.
- If the noncompliant versions are released to multiple tracks, repeat step 1 on each track.
- You can check the App bundle explorer page again, and the noncompliant version code should show as “Inactive” and “0 releases” in the details page.
If all declared use cases are impacted, the FOREGROUND_SERVICE permission must also be removed.
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.