Repository navigation
|
My app was flagged or rejected on Google Play for this. READ_MEDIA_IMAGES or READ_MEDIA_VIDEO declared without the Android photo picker. Which guideline is this, how do I find it in my project, and how do I fix it before I resubmit? |
Replies: 1 comment
|
Guideline. Photo and Video Permissions (Google Play) Severity in the playbook. high What triggers it. Apps targeting API 33 or higher may only request READ_MEDIA_IMAGES and READ_MEDIA_VIDEO when the system photo picker is not sufficient for core functionality, and every app that keeps them must complete the Photo and Video Permissions declaration in Play Console. A manifest that declares them with no photo picker usage in source is the usual rejection shape. What to search your code for. How to fix it. Use the Android photo picker for one-off selection. Keep broad access only for a core gallery-style feature and complete the Photo and Video Permissions declaration in Play Console. Reference https://support.google.com/googleplay/android-developer/answer/14115180 The guard reports this as This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
Guideline. Photo and Video Permissions (Google Play)
Severity in the playbook. high
What triggers it. Apps targeting API 33 or higher may only request READ_MEDIA_IMAGES and READ_MEDIA_VIDEO when the system photo picker is not sufficient for core functionality, and every app that keeps them must complete the Photo and Video Permissions declaration in Play Console. A manifest that declares them with no photo picker usage in source is the usual rejection shape.
What to search your code for.
READ_MEDIA_IMAGES,READ_MEDIA_VIDEOHow to fix it. Use the Android photo picker for one-off selection. Keep broad access only for a core gallery-style feature and complete the Photo and Video Permissions …