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:

<uses-permission android:name="android.permission.CAMERA" /> <uses-permission android:name="android.permission.RECORD_AUDIO" />

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?

Hammad Hasan's user avatar

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.