Karumi/Dexter

ACTIVITY_RECOGNITION Permission

Open

#280 opened on Jun 9, 2021

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (5,224 stars) (682 forks)batch import
bughelp wanted

Description

Expected behaviour - Work correct :)

Actual behaviour - Dosnt work.

Steps to reproduce -

After clicking on permission dialog deny button close app and open again . And after that when you clicking allow or deny button it dosnt call onPermissionDenied or onPermissionRationaleShouldBeShown function. This happening only with ACTIVITY_RECOGNITION permission, i try it with location,camera, phone and other permissions, all work.

Version of the library-6.2.2

Contributor guide

Tech stack
javaandroid
Domain
mobile
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Android development environmentknowledge of runtime permissionsfamiliarity with Dexter library
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Reproduce the issue on a device or emulator running Android 10+ (where ACTIVITY RECOGNITION permission exists). Examine Dexter's permission handling logic in the `PermissionManager` and `AndroidPermissionService` classes, particularly the flow after deny. Check if the problem is related to the permission being categorized as 'special' or 'dangerous'. Consider testing with a minimal sample app to isolate the bug. Review any linked pull requests or comments for clues.
ACTIVITY_RECOGNITION Permission · Karumi/Dexter#280 | Good First Issue