I use "App Lock" to secure access to my file manager. I use "File Commander" from Google Play Store.
The bug occurs when using App Lock with File Commander.
File Commander opens normally after unlocking it with App Lock. However, once I am on the File Commander home screen and tap one of the internal sections — for example Images, Music, Videos, Documents, Downloads, File Converter, Trash, or PC File Transfer — App Lock immediately asks me to unlock File Commander again.
After unlocking, the selected section still does not open. Instead, I am returned to the same state and App Lock keeps asking for authentication again and again. This creates an endless unlock loop.
It seems that App Lock detects File Commander’s internal sections or activities as a new app launch and locks them again, instead of keeping File Commander unlocked after the initial authentication.
The same type of problem also happens with the Google Play Store: after unlocking the Play Store, tapping an app listing causes App Lock to request authentication again, resulting in a similar loop.
This does not appear to be a user error. It looks like App Lock is not correctly handling apps that open internal subpages, activities, or modules after the main app has already been unlocked.
I use "App Lock" to secure access to my file manager. I use "File Commander" from Google Play Store.
The bug occurs when using App Lock with File Commander.
File Commander opens normally after unlocking it with App Lock. However, once I am on the File Commander home screen and tap one of the internal sections — for example Images, Music, Videos, Documents, Downloads, File Converter, Trash, or PC File Transfer — App Lock immediately asks me to unlock File Commander again.
After unlocking, the selected section still does not open. Instead, I am returned to the same state and App Lock keeps asking for authentication again and again. This creates an endless unlock loop.
It seems that App Lock detects File Commander’s internal sections or activities as a new app launch and locks them again, instead of keeping File Commander unlocked after the initial authentication.
The same type of problem also happens with the Google Play Store: after unlocking the Play Store, tapping an app listing causes App Lock to request authentication again, resulting in a similar loop.
This does not appear to be a user error. It looks like App Lock is not correctly handling apps that open internal subpages, activities, or modules after the main app has already been unlocked.