Short answer
If your app targets Android 13 or later, it may only request READ_MEDIA_IMAGES and READ_MEDIA_VIDEO when a system picker such as the Android photo picker isn’t enough for its core functionality, as with a gallery app. If people only choose a photo or video to attach or upload, switch to the photo picker and remove both permissions. If a library adds them, remove them in your manifest with tools:node="remove". If the app really needs broad access, submit the declaration in Play Console.
What to check, in order
01
Picking a photo doesn’t need broad access
“may only request the READ_MEDIA_IMAGES and READ_MEDIA_VIDEO permissions if system pickers (like the Android Photo Picker), are not sufficient for your app to provide core functionality.” Google Play, Understanding Restricted Permissions
If the app lets people choose a profile picture, attach an image or upload a video, the photo picker covers it and gives the app only the items people select. Switch to it, remove both permissions from the manifest, and upload a new build.
02
A library adds the permission, not your code
“an element in your merged manifest that you don't need that was provided by a lower-priority manifest file that's out of your control (such as an imported library)” Android Developers, Manage manifest files
In Flutter, Expo and React Native apps, a plugin’s own manifest can bring a permission into your build that you never wrote. Open the Merged Manifest tab in Android Studio to see which file it comes from, remove it in your app’s AndroidManifest.xml with tools:node="remove" on that permission (we declare xmlns:tools on the manifest root so it builds), then test the feature that used it.
03
A custom picker on its own doesn’t qualify
“Apps that have custom pickers are not automatically qualified to use the permission” Google Play, Understanding Restricted Permissions
Your own in-app gallery screen isn’t a reason by itself. To keep the permissions, submit the declaration in Play Console and explain why the Android photo picker or another system picker isn’t sufficient for the app.
04
Apps that really need broad access
“Apps whose core function includes managing and maintaining all of users' photos/videos (such as "gallery apps") would need broad access on a user's device.” Google Play, Understanding Restricted Permissions
If managing all of someone’s photos or videos is what the app is for, keep the permissions and complete the declaration in Play Console with that reason. Google also exempts private and enterprise device management apps.
05
The app breaks when someone says no
“you must make a reasonable effort to accommodate users who do not grant broad access to media files on their device.” Google Play, Understanding Restricted Permissions
Even with broad access approved, the app has to keep working for people who decline it. Offer the system picker for the same feature, or a reduced version of it, instead of a dead end.
Checked against the vendor’s docs on : Google Play Help: Understanding Restricted Permissions with minimum scope alternatives; Android Developers: Photo picker; Android Developers: Manage manifest files.
Rather hand it over?
Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.
Related: Google Play Data safety form rejected · Google Play 12 testers for 14 days · Target API 36 on Google Play · Google Play foreground service declaration