bluelinelabs / bluelinelabs/Conductor
Unexpected behaviour of android.app.Fragment.requestPermissions
- Dominant language
- Java
- Stars
- 3.9k
- Forks
- 338
- PR merge metrics
- No merged PRs in 30d
Description
I use Conductor in my project and noticed probably unexpected behavior when working with runtime permissions. With androidx.Fragment or AppCompatActivity if you try to start another one request with the same id, previous request will be automatically cancelled by Android. But android.app.Fragment does not do this (at least on Android 7 and 8), it invokes onRequestPermissionsResult() method twice.
PR with mergating to AndroidX Fragments: https://github.com/bluelinelabs/Conductor/pull/602
Contributor guide
Research direction
Review the reported behavior of android.app.Fragment.requestPermissions on Android 7 and 8, then examine the AndroidX Fragments migration in PR #602. Confirm how repeated permission requests are handled and whether the migration addresses the duplicate onRequestPermissionsResult() callbacks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100