FOREGROUND_SERVICE_MEDIA_PLAYBACK app rejection multiple times in 4 months

In the last 4 months, my app has repeatedly encountered issues with the ‘FOREGROUND_SERVICE_MEDIA_PLAYBACK’ rejection. The Bubble.io fix works temporarily, but the problem keeps resurfacing. Is there a permanent solution?"

@nick.carroll Need your help.

I’m facing the same issue with my app. The FOREGROUND_SERVICE_MEDIA_PLAYBACK permission is not part of my app’s core functionality, yet it keeps being included in the build. I’ve tested both with and without plugins, and the permission still does not go away.

Does anyone in the group please help me?

No update so far.

Message from Bubble team- it’s still actively being worked on by our specialized team.

No update yet. The specialist is still looking into it, and today marks the 10th day.

@supportdept @help

Still no update. 10th day.

@josh

i am also having this
android.permission.FOREGROUND_SERVICE_MEDIA_PLAYBACK problem. so there is nothing i can do? nothing to do with the plugins?

nothing to do with the plugins. It’s something on bubble’s end

Finally, after multiple follow-ups and a lot of frustration, Bubble.io resolved the issue—my app is now live again.

@daviyuri @justinng9392 Create a new build and check if it resolves the issue.

Before submitting your app to the Play Store, check the manifest file inside the .aab. If unwanted or undeclared permissions are present FOREGROUND_SERVICE_MEDIA_PLAYBACK, your app may be rejected unless they’re removed and it can only done by Bubble engineering team.

Hi everyone, sorry for the delay in responding here. This issue was due to adding a new library to support some plugins that also required this permission. Google has gotten more strict about these types of permissions and thus were blocking apps that weren’t describing why they needed the permission.

We have unblocked apps from hitting this issue and will be releasing a new permissions toggle in the settings tab for those that are using an audio plugin that actually require this permission. Sorry again about the submission issues.

Thank you @nick.carroll Hoping, as you mentioned, we’ll have a toggle soon. Fingers crossed.