Details on Google Play's Photo and Video Permissions policy - READ_MEDIA_IMAGES and READ_MEDIA_VIDEO

[XorPP]

I am reaching out regarding Google Play’s updated Photo and Video Permissions policy, which enforces stricter rules on apps using the READ_MEDIA_IMAGES and READ_MEDIA_VIDEO permissions. The policy requires developers to either migrate to using the Android photo picker for one-time or infrequent access or submit a declaration for core/broad access if frequent and persistent access is needed.
(https://support.google.com/googleplay/android-developer/answer/14115180)

As a user of the following plugins in my Cordova-based app:

cordova.plugins.diagnostic
cordova-plugin-file
cordova-plugin-camera
I’d like to know:

Do any of these plugins currently use the READ_MEDIA_IMAGES or READ_MEDIA_VIDEO permissions?
If so, are there plans to update these plugins to comply with the new Google Play policy by migrating to a system picker or another alternative approach?
Is there anything I, as a developer, need to update or modify in my app's implementation when using these plugins to remain compliant with the policy?
Your guidance will help ensure my app meets the compliance deadline and avoids any disruptions on Google Play.

Thank you in advance for your assistance. I look forward to your response.

[breautek]

cordova-plugin-file
cordova-plugin-camera

The latest versions of these plugins do not use the READ_MEDIA_* permissions anymore.

See the Camera 8.0.0 and File 8.1.3 notes for more information.

It's particularly important to check the release notes of the Camera plugin as it does introduce breaking changes that may affect your application and may require additional action, depending on how the camera plugin is being used.

It's recommended to use the latest version the File plugin as it contains fixes related to co-interaction with the Camera API, ensuring consistent behaviour between Android and iOS platforms.

cordova.plugins.diagnostic

This isn't a plugin maintained by Apache, so you'll need to reach out to that plugin's author(s).

Is there anything I, as a developer, need to update or modify in my app's implementation when using these plugins to remain compliant with the policy?

Generally speaking, READ_MEDIA_* permissions are only necessary if the nature of your application requires broad access to those kind of media assets. e.g. if you're application is a gallery app, then having READ_MEDIA_IMAGES permission might make sense and you can provide Google with reasonable justification.

Historically, Cordova required the READ_MEDIA_* permissions because we used older APIs that required broad consent to use, for legacy reasons. But from a library perspective, it's not safe to assume that the application fits the criteria that is acceptable to use these permissions. Therefore we (Apache) has since refactored to use modern practices so that we don't need broad permissions.

The main breaking point here is the application no longer has persistent access to all media files. If you pick images from the photo album/gallery, the application is granted temporary access to that specific file that the user has picked using the photo picker. Therefore the application will need to make a copy if necessary to retain access to that asset. A prime example of this is if you're letting the user pick a profile picture for your application.

Some applications may not need to retain a copy and can safely use the image directly as is. For example, an image editing application might temporary use the picked image, and only save the modified result. So it all depends on the nature of your application here.

Also to note that currently there are some other Apache plugins that isn't mentioned but are still using READ_MEDIA_* permissions, their refactors are still a work in progress.

[XorPP]

Thank you for the detailed information.

I'll review the release notes for Camera 8.0.0 and File 8.1.3 to address any breaking changes and ensure compliance. I'll also confirm if my app's functionality requires READ_MEDIA_* permissions, as they are now less broadly needed. For temporary media access, I'll implement appropriate handling, such as copying files if retention is necessary. Also, I'll monitor updates for other Apache plugins still using READ_MEDIA_* permissions to remain aligned with modern practices.

Best regards