LuckSiege / LuckSiege/PictureSelector
Google Play's update Photo and Video Permissions policy
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 13.6k
- Forks
- 3.1k
- PR merge metrics
- No merged PRs in 30d
Description
Photos and videos on a user’s device are considered [Personal and Sensitive User Data](https://support.google.com/googleplay/android-developer/answer/10144311#personal-sensitive) and should be treated with utmost privacy best practices. This sensitive information leaves users vulnerable to leaks or targets of exploitation, so minimizing this access helps avoid the burden on developers of handling such sensitive data. To further support protecting users’ privacy, we [introduced policy](https://support.google.com/googleplay/android-developer/answer/13986130) to limit the scope of how broad access to photos and videos can be acquired on Google Play. Only apps with a need for broad access to photos will be allowed to maintain the READ_MEDIA_IMAGES and READ_MEDIA_VIDEO permissions. Apps with a one-time or limited use of photo and video files are requested to use a system picker such as the [Android photo picker](https://android-developers.googleblog.com/2023/04/photo-picker-everywhere.html).
Help me please ^ . ^
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. Start by locating the Android permission handling for READ_MEDIA_IMAGES and READ_MEDIA_VIDEO, then review the linked Google Play policy and Android photo picker guidance. Done means the library's photo and video access follows the stated policy, but the issue does not define the required implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100