[android] Google Play Rejection: "Connected Device" FGS requirement for Zoom SDK

[miarevalo10]

Hi everyone,

We are currently facing a Google Play Store rejection regarding the Connected Device Foreground Service Type (specifically CONNECTED_DEVICE). This service is triggered by the Zoom SDK to handle Bluetooth/external audio during meetings.

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.

• Posted same issue on Zoom's forum https://devforum.zoom.us/t/android-permission-foreground-service-connected-device-playstore-is-rejecting-this-permission/140436

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.

[mieszko4]

It might be more related to Zoom's forum. So I gave some suggestions there.