keepassium
FaceID unlock gets retriggered and loops when trying to choose password
Description The "autofill-sheet" keeps looping when trying to choose a password from the entries. Multiple websites and databases tested, with both a database that was created on Linux via latest KeePassXC (which used to work earlier) and a new test database that was created through KeePassium Pro itself exhibiting this behavior. Check attached video for example.
How to reproduce Steps to reproduce the behavior:
- Go to a website with a login page (e.g. https://id.galaxus.eu); the specific website doesn't matter
- Tap on "passwords" on the iOS keyboard to bring up the password entry choice
- Let FaceID unlock the database and wait a second without selecting anything
- FaceID unlock gets retriggered and continues to loop (see attached video file)
Expected behavior Should be able to freely browse, check and select the entries of the database like it used to work
Video
https://github.com/user-attachments/assets/07af1e89-71de-4b3c-bf06-5de3cbae2144
Environment:
- Device: [iPhone 16 Pro]
- OS: [iOS18.4]
- App Version: [v2.3.163 Pro]
Additional Info Everything works as it should if pin unlock is used instead of FaceID. Furthermore, this bug didn't show up before the latest iOS 18.4 update.
i just recently switched from strongbox zero to keepassium pro and encountered this issue too. i have 3 databases used, and if i try to login on a website and do an auto fill via keepassium, it loops the face id unlock or passcode unlock screen even on the database selection screen. the only way for me to stop this behavior is to disable app protection which is not even considerable as a workaround.
Hi everyone, sorry for the long delay, got a bit swamped with emails…
This looks like a comeback of #266, I guess Apple tweaked the animation of Face ID prompt again. So by the time Face ID popup finishes animating, KeePassium thinks it's time to lock up again.
As a quick workaround, open app settings → App Protection → Timeout → increase it from "Immediately" to "3 seconds". In the meanwhile, we'll think of a proper solution…
Hey, that works, thanks!
Maybe it’s better to just remove “Immediately” then, I don’t think a small delay can make it any less secure.
