Locking while using autofill leads to issues next invokation about keepassium HOT 6 CLOSED

A-OK here!

Issue no longer seen with beta 23!

from keepassium.

For me, this is reproducible with 100% rate, in all of the grand total of two apps I've tried it in, but I believe there may be some configuration related parameters to this as well. Let me know if there's any config-export or log entries you want me to attach/send you.

from keepassium.

Yep, I can reproduce this, too. I will take a closer look once I’m back at my dev machine on Monday. Thanks!

from keepassium.

I'm not ruling Apple's code out here, as it seems a bit strange to me that the KeePassium prompt for TouchID shows up before even being asked what source to use (iCloud/KeePassium).

I did however try with the only other app autofill enabled app I have, Saaspass, and it does not show the same behavior, working fine repeatedly even when locking the screen after unlocking the database. Saaspass does use TouchID for its main app, but it does not show up when used in the autofill context.

from keepassium.

It was a combination of me and Apple :)

I usually test AutoFill in Safari. There, as soon as AutoFill UI closes, the system kills its process. Apparently, when AutoFill is used in an app, the AutoFill process lives longer. So when you re-open AutoFill and it tries to load the last used database — there is already an open database! This triggered one of the failsafes, and the extension crashed.

@magebarf please let me know if the issue remains in beta 23 and I will reopen. Thanks!

from keepassium.

Great, thanks!

from keepassium.