Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Routine operations are blocked if Screen Lock options in enabled #1408

Open
3 tasks done
OmarKSH opened this issue Jul 12, 2024 · 0 comments
Open
3 tasks done

Routine operations are blocked if Screen Lock options in enabled #1408

OmarKSH opened this issue Jul 12, 2024 · 0 comments
Labels
Bug Something isn't working Priority: 3 Severity: 2 Status: Accepted Accepted or approved feature/issue
Milestone

Comments

@OmarKSH
Copy link

OmarKSH commented Jul 12, 2024

Please check before submitting an issue

  • I know what my device, OS and App Manager versions are
  • I know how to take logs
  • I know how to reproduce the issue which may not be specific to my device

Describe the bug

When running a routine operation using the "am" command as described by the docs while having the Screen Lock option enabled in AppManager the user is asked to unlock the app before executing the operation.

To Reproduce

  1. Go to profiles and create a profile adding a few applications to it and enabling routine ops for it in its configuration menu
  2. Go to settings -> Privacy -> Toggle "Screen Lock" option as enabled
  3. Try to run the profile using the "am" command as mentioned in the docs
  4. Instead of the Routine Operation running automatically, it opens AppManager and requests you to unlock the application

Expected behavior

The Expected behavior is for the routine operation to run automatically without user interaction

Screenshots

No response

Logs

No response

Device info

  • Device: Samsung Galaxy S10e
  • OS Version: 13
  • App Manager Version: 3.1.6
  • Mode: Root

Additional context

No response

@OmarKSH OmarKSH added the Bug Something isn't working label Jul 12, 2024
@MuntashirAkon MuntashirAkon added this to the v4.0.0-beta02 milestone Jul 12, 2024
@MuntashirAkon MuntashirAkon added Priority: 3 Severity: 2 Status: Accepted Accepted or approved feature/issue labels Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Priority: 3 Severity: 2 Status: Accepted Accepted or approved feature/issue
Projects
None yet
Development

No branches or pull requests

2 participants