LuckSiege / LuckSiege/PictureSelector
权限问题
- Dominant language
- Java
- Stars
- 13.6k
- Forks
- 3.1k
- PR merge metrics
- No merged PRs in 30d
Description
## Current use version?
#### 当前使用的版本是多少?
```
v3.11.2
```
## Will this problem occur in demo?
#### Demo能否复现这问题?
```
不能
```
## Describe the problem or provide an error log?
#### 描述问题或提供错误log?
```
新安装的app就是我如果没有读写权限的情况下,我直接触发就是打开相机功能,然后库里会帮我申请一个相机权限,但是我正常拍照后
走的是.forResult 方法的OnResultCallbackListener中的onCancel 就是说我不能拿到这拍照后的图片地址啊, 但是现在新规定不让连续申请两个权限就很离谱啊
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the camera-permission flow described in the issue, including the .forResult path and its OnResultCallbackListener.onCancel callback. Reproduce the behavior with a newly installed app without read/write permission; done means a successful camera capture still exposes the captured image address instead of only invoking onCancel.
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
- 25/100