Alex-Popappa
Original Poster
Feb 6, 2025

Foreground service permissions stuck in a loop

Hello,

we have the following issue and we think there is a bug on Google Play Console.
In July 2024 we have submitted the correct permission on Google Play console:

android.permission.FOREGROUND_SERVICE_DATA_SYNC
checked the "other case" : We have Provided a video demonstrating how the app uses the FOREGROUND_SERVICE_DATA_SYNC permission for the tasks  selected
The video was approved by Google, Manifest file and all the logic inside the app worked fine from summer.

Tens of releases where sent in review and approved since that with no issues.

This until the current week, we released a new version (1.37) (correctly approved) and after a couple of days a new one  (1.38) (just with a small difference in a xml button layout) nothing changed in any other logic, permissions in the manifest are always the same together with the foreground service.

We received the email of rejection:
Your in-app experience or video does not match the Data Sync - Local Processing: Other in your declaration.

I have submitted an additional updated video made with the latest version of the app, showing the need of the foreground service and the fact that the user has to approve this (overlay app) and also can stop the foreground service at any moment. This behaviour is the same since last summer, really nothing has changed from the last Google decision, you can check the video here:


Immediately we have received another rejection, so we discarded the release that was in review (1.38) with that app bundle and submitted the video again.

Immediately we have received another rejection:
  • Your in-app experience or video does not match the Data Sync - Local Processing: Other in your declaration.
Issue details
We found an issue in the following area(s):
  • Version code 137

 but now the release mentioned is the current on track available to all users that was approved one week ago (1.37), if we submit a new video we immediately continue to receive this rejection.

We hope there is someone at Google Play Console that can help us since the opened case is not yet solved.


Details
Google Play Console,Fix an issue
Community content may not be verified or up-to-date. Learn more.
All Replies
BenMcc
Diamond Product Expert
PE: Play Console - Here for the fun of it!
Feb 6, 2025
Hi,

If you think the video does demonstrate it and your app falls into that permission criteria then you will need to make an appeal. The appeals team will review it all and make a decision.

Ben
BenMcc
Diamond Product Expert
PE: Play Console - Here for the fun of it!
Feb 12, 2025
Be aware pausing a test track DOES NOT deactivate a bundle. But however if you get a rejection then you will need to appeal and tell the appeals team that you are following the advice of the last appeal (and give them the last appeal number). Try that once and if that does not work then let me know the new appeals number.
Alex-Popappa
Original Poster
Feb 12, 2025
Pending modifications were approved after our legal has prepared the letter.
We hope that if we release any other change it will not fall in the same rejection loop.
I suggest to explain the reason of rejection in particular when there is such delicate and intrepretable documentation, especially when they involve app content/privacy and their approval is vital for an app.

Last edited Feb 12, 2025
false
17821478304935117743
true
Search Help Center
true
true
true
true
true
92637
false
Search
Clear search
Close search
Main menu