Google Play READ_MEDIA_IMAGES Rejection: How to Fix

What this rejection means

The app requests READ_MEDIA_IMAGES or READ_MEDIA_VIDEO, which Google keeps for apps whose core feature is browsing or editing media. An app that only lets people pick a photo now and then must use the Android photo picker, which needs no permission.

Why reviewers send it

Broad access to photos and videos is reserved for apps built around media, such as galleries and editors. Apps that let people pick an image now and then must use the Android photo picker, which needs no permission.

The message Google Play sends

Issue found: Violation of Photo and Video Permissions policy

Your app requests the READ_MEDIA_IMAGES permission but only needs one-time or infrequent access to photos. Use the Android photo picker instead.

The exact wording changes from one review to the next; the policy name is what to look for.

How to fix it

Remove READ_MEDIA_IMAGES, READ_MEDIA_VIDEO and READ_EXTERNAL_STORAGE from android/app/src/main/AndroidManifest.xml if the app only picks photos occasionally.
Pick images through the Android photo picker.
If media access is the app’s core feature, fill in the photo and video permissions declaration in Play Console instead.
Upload a build with a higher version code.

Fix it with Lovable, Bolt or Cursor

If the app was built with an AI builder, paste this into it, then check the result on a phone:

In android/app/src/main/AndroidManifest.xml, remove READ_MEDIA_IMAGES, READ_MEDIA_VIDEO and READ_EXTERNAL_STORAGE, and choose images through the Android photo picker, which needs no permission.

What to tell Google Play

Replace the [brackets] with what you actually changed:

We removed the READ_MEDIA_IMAGES and READ_MEDIA_VIDEO permissions. The app now uses the Android photo picker to choose images.

Got a different message?

Paste the whole rejection into the rejection explainer. It recognises this one and 26 others, in your browser — nothing is uploaded.

Google Play photo and video permissions policy