My Authenticator is blocked, but I didn’t block it
If your authenticator app (such as Google Authenticator, Microsoft Authenticator, or similar) is being blocked even though you didn’t add it to a blocklist, the cause is almost certainly Block device settings being active in Strict Mode.
Why this happens
Authenticator apps need access to certain device settings to verify your identity. When Block device settings is enabled in Strict Mode, it restricts that access — which can make the authenticator appear blocked or broken, even though you never blocked it directly.
How to fix it
You’ll need to deactivate Strict Mode first:
- Open AppBlock.
- Go to Strict Mode.
- Fulfill your access method (PIN, Charger, Timer, etc.).
- Once Strict Mode is off, your authenticator should work again.
If you cannot deactivate Strict Mode on your own, go to Profile → Help → Contact support and select Emergency unblocking.
Good to know
If you regularly need your authenticator while Strict Mode is active, consider turning off the Block device settings option before reactivating Strict Mode — or use the Show Available Settings option (Profile → Customize → Blocking preferences → Show Available Settings), which lets some parts of Settings remain accessible.
