GitHub user breautek added a comment to the discussion: Details on Google Play's Photo and Video Permissions policy - READ_MEDIA_IMAGES and READ_MEDIA_VIDEO
@robertohonk my best advice is to first check `platforms/android/app/src/main/AndroidManifest.xml` to confirm that `READ_MEDIA_IMAGES`, `READ_MEDIA_VIDEO`, or `READ_MEDIA_AUDIO` is not actually present. If it is, you may have another plugin or something manipulating the manifest and declaring these permissions. If your manifest is clear of these permissions, then I'd double check all your tracks on google play. If you have an older build on an internal test track or something, it will cause Google Play to treat your app as an app using those permissions. This is something that personally got me, having an older build in an internal test track. If this is the case, deploying your newer app and publishing to those tracks is necessary to replace the older builds on those tracks. GitHub link: https://github.com/apache/cordova/discussions/520#discussioncomment-13009491 ---- This is an automatically sent email for issues@cordova.apache.org. To unsubscribe, please send an email to: issues-unsubscr...@cordova.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
