android.permission.FOREGROUND_SERVICE_CONNECTED_DEVICE Playstore is Rejecting this permission

Meeting SDK
1

Hi Zoom Team and Community,

Our Android app using Zoom Meeting SDK v6.6.9.35200 is being rejected by
Google Play due to FOREGROUND_SERVICE_CONNECTED_DEVICE permission.

Issue:

  • Google requires this permission ONLY if external devices are core functionality
  • Our app uses built-in camera/mic only (no external Bluetooth/USB devices)
  • Cannot remove permission without SDK crashing
  • Cannot publish updates to Google Play

Has anyone else encountered this with Android 14 policy enforcement?
Is there a workaround or SDK configuration to disable connected device support?

This is blocking our production release. Any guidance appreciated!

Thanks!

2

Hi! We’re also facing the same issue.

Google has rejected our FGS declaration, stating:

“Please update the in-app experience so that the related FGS functionality is either initiated by the user or perceptible to the user…”

What we have tried:

  • Declaration Update: Submitted a video showing the SDK using Bluetooth during a live meeting.

  • In-App Disclosure: Added a pre-meeting modal explaining why the permission is needed and asking for user consent before joining.

Despite these changes, Google continues to claim the FGS functionality is not “perceptible” or “user-initiated” enough.

  • Has anyone successfully navigated this specific rejection with the Zoom SDK?

  • Did you have to move the FGS initiation to a specific user action (e.g., a “Connect Bluetooth” button)?

  • Is there a specific way to make the background activity more “perceptible” to satisfy the latest Play Store policies?

Any insights or examples of accepted declaration videos/disclosures would be greatly appreciated.

3

Gemini suggests to have persistent notification which sounds as something that makes sense to me.

User Perceptibility: The user must be aware that the service is running via a persistent notification.

Does persistent notification show to you?

In any case, would be great if Zoom

  1. had an option to not use bluetooth speaker which would avoid need to enforce this permission
  2. made sure that it handles persistent notification or give a guide on how to handle it by dev using Zoom SDK

@chunsiong.zoom Any thoughts here?