Mesibo SDK adds READ_MEDIA_IMAGES / READ_MEDIA_VIDEO causing Google Play rejection
04:25 01 Dec 2025

I’m using the Mesibo SDK for video and voice calls in my Android app. My own AndroidManifest.xml does not include any media permissions.I only use:



However, when I upload my app to Google Play, it gets rejected under the Photo and Video Permissions policy because the merged manifest contains:

android.permission.READ_MEDIA_IMAGES
android.permission.READ_MEDIA_VIDEO

Google says my app does not have a core use case requiring persistent access to photos/videos (which is true. I only do live video/voice calls).

I suspect Mesibo’s internal manifest is automatically adding these permissions through manifest merging.

How can I prevent Mesibo from adding READ_MEDIA_IMAGES and READ_MEDIA_VIDEO to my final merged manifest? Is there a recommended solution from Mesibo to disable or remove these permissions?

android permissions google-play mesibo