Closed pheki closed 8 months ago
This is a side effect of how WorkManager works. We request root in the Application class, to have it available ASAP, and although we're not actually performing the update checks, our app still starts to run the schedule, thereby requesting root access.
However, the app will exit without executing anything else once it determines automatic update checks are shut off.
Also, please note the latest version is 2.3.6, and fdroid may have outdated builds currently
Hey, thanks for maintaining this!
Also, please note the latest version is 2.3.6, and fdroid may have outdated builds currently
That's interesting, the badge on README.md shows 2.3.4 and that's also the latest git tag / Github Release
although we're not actually performing the update checks, our app still starts to run the schedule, thereby requesting root access
What other apps seem to do is to cancel the schedule when the user disables periodic checking, and re-enable it if the user enables it again.
Where the periodic checking is enabled: BackgroundUpdateChecker.kt#L476 API to cancel: WorkManager.cancelUniqueWork API to re-enable (already used to schedule): WorkManager.enqueueUniqueWork
Describe the bug AMM asks for root in the background even when both
Automatic modules update check
andCheck for app updates
are disabled. It happens on reboot and also every once in a while (I believe it's at least once a day).To Reproduce Steps to reproduce the behavior:
Automatic modules update check
andCheck for app updates
Expected behavior No background activity if automatic updates are disabled, especially no requests for root access.
Screenshots
Device info: