Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comply with new Google Play's Photo and Video Permissions policy - removal of READ_MEDIA_IMAGES and READ_MEDIA_VIDEO permissions #2486

Open
fabiendem opened this issue Apr 16, 2024 · 3 comments

Comments

@fabiendem
Copy link

fabiendem commented Apr 16, 2024

Motivation

Google announced a new Google Play's Photo and Video Permissions policy.
The full details are available at https://support.google.com/googleplay/android-developer/answer/14115180?hl=en

This is mainly about upcoming changes around the READ_MEDIA_IMAGES and READ_MEDIA_VIDEO permissions.

Quoting:

  • Mid 2024: Apps with one-time or infrequent use of photos requested to use a system photo picker and remove READ_MEDIA_IMAGES and READ_MEDIA_VIDEO permissions from their app manifest.
  • Early 2025: Only apps with broad access core functionality can use READ_MEDIA_IMAGES and READ_MEDIA_VIDEO permissions.

Apps using those permissions for the Stream Chat feature are likely to fall into this "one-time or infrequent use of photos" bucket.
See https://support.google.com/googleplay/android-developer/answer/14115180?hl=en#zippy=%2Cwhat-does-it-mean-to-have-a-one-time-or-infrequent-use-of-photos-or-video-files

What does it mean to have a one-time or infrequent use of photos or video files?
Examples of one-time or infrequent use of photos or video files include, but are not limited to, uploading a profile picture, uploading an image for a playlist, or uploading a photo of a check for banking purposes. Infrequent use infers that your app does not have a photo or video use case as its core functionality. If your app has a one-time or infrequent use case for photo or video files, you may not use the READ_MEDIA_IMAGES or READ_MEDIA_VIDEO permission, and we urge you to instead use a system picker to preserve user privacy.

Proposed solution

Google suggests using a system picker, such as an Android photo picker.
See https://support.google.com/googleplay/android-developer/answer/14115180?hl=en# and https://developer.android.com/training/data-storage/shared/photopicker

Acceptance Criteria

Apps using the Stream SDK will stay compliant by 2024/Early 2025.
Stream SDK switches to a system picker or an alternative method, so we no longer use the READ_MEDIA_IMAGES and READ_MEDIA_VIDEO permissions.

@khushal87
Copy link
Member

Hey @fabiendem, for this to happen, we will have to wait for our dependencies like react-native-cameraroll and expo-media-library to be compliant first and then we can add the following support as well.

FYI: we use these libraries for our image picker.

@fabiendem
Copy link
Author

Hi @khushal87, thank you. Are you working in collaboration with the maintainers of those libs?
Do you plan to raise the issue there?

@fabiendem
Copy link
Author

Posted at react-native-cameraroll/react-native-cameraroll#618

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants