It’s Cybersecurity Awareness Month! Join our interactive training session, or learn about security and AI from 1Password experts.
Forum Discussion
Solved
Biometric unlock not working: That didn't work. Check your password and try again
Hello!, I am experiencing an issue where my android app keeps failing to login with biometrics and when I login with master password it will also keep MFAing me. I enter it time and time again, b...
The issue is still open with our development team and they continue to investigate. The problem seems limited to Motorola's Edge and Razr Series.
While I don't have an ETA on when this will be resolved, keep 1Password, and your Motorola device, updated so that you receive the fix as soon as it is developed and released:
-Dave
1P_Timothy
Community Manager
Community ManagerHi birchyboy01, thanks for the update!
Our ongoing investigation into this bug suggests an issue with a device driver may be, at least partially, the cause. If that's case, it looks like a recent patch to that driver is correcting the issue. If you start seeing this behavior again, let us know, Thanks again!
As a matter which may be of use to your Dev's, my biometric logon failed again, even after reinstallation and altering all the unlock parameters, again.
However, I remembered that I had cleared all the Android cookies. I then checked my device Security controls and found that 1Password was not available for autofill. I added it to the available autofills, re-authorised it.
It seemed to me that part of the problem is the Motorola Edge Pro option to require a Return code after the PIN or not. When I set it to be not required and rebooted, 1Password biometric WORKED.
So it may be related to the cookie clearing, the Return code or both.
It's happened AGAIN, for no apparent reason. Biometric unlock failed.
However, I tried the cache clearing and then the Android settings>Security and Privacy>Device unlock>Screen lock> set Auto-confirm unlock to ON (slightly less secure than tapping Enter to confirm). It worked. Again. This seems to be the fix, at least on my Edge 50 Pro.
