LuckSiege / LuckSiege/PictureSelector

鸿蒙3 的适配问题

Open
#2,986 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
13.6k
Forks
3.1k
PR merge metrics
No merged PRs in 30d

Description

![Image](https://github.com/user-attachments/assets/7ee125c1-71d8-4ee6-978e-b9087a0e33e7)

如图,此框架的处理是 Android13 之上申请单独的图片权限,13 之下申请读写权限,这本身没有问题,但是 鸿蒙早期版本属于基于 Android10 的分叉,但是它又把 Android 13后续更新的新特性给做上了,就会有这个问题

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the permission behavior shown in the attached image on HarmonyOS 3, then inspect the Android 13+ and pre-Android 13 permission handling. The fix is complete when HarmonyOS 3 requests the appropriate permissions without applying the Android 13+ image-permission path incorrectly.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.