KeePassium icon indicating copy to clipboard operation
KeePassium copied to clipboard

macOS: Quick AutoFill is broken

Open TheFrenchGhosty opened this issue 1 year ago • 2 comments

Description

When using Quick AutoFill in Safari on macOS, the dialog will pop up, but when the KeePassium "box" open, nothing will work and it will be stuck on an empty screen, this box isn't possible to be closed, so Safari has to be quit.

Using "normal" AutoFill works, it only happens with Quick AutoFill.

How to reproduce

  • Go to a website you have credentials for
  • Try to use QuickAutofill

Expected behavior

It works (and the window can be closed)

Screenshots

Screenshot-2024-10-12-17-13-52@2x

Environment:

  • Device: mac
  • OS: macOS Sonoma
  • App Version: 1.53 (latest)

Additional context

Maybe related to https://github.com/keepassium/KeePassium/issues/259

TheFrenchGhosty avatar Oct 12 '24 15:10 TheFrenchGhosty

Did you import a Keepass database that was created elsewhere? I had this happen and the issue was that the autofill functionality here has some limitations (memory usage??) and you need to change your Keepass database to the default Keepassium encryption settings: ChaCha20, Argon2d, 100 rounds, 1MB memory usage, 2 threads

That solved the problem for me

feld avatar Oct 14 '24 15:10 feld

@feld

Did you import a Keepass database that was created elsewhere?

I am using the same database as I'm using in KeePassXC yes, it was created in KeePassXC

you need to change your Keepass database to the default Keepassium encryption settings: ChaCha20, Argon2d, 100 rounds, 1MB memory usage, 2 threads

I'd rather use the default from KeePassXC... those should work if the DB is unlocked already (it works on iPadOS)

TheFrenchGhosty avatar Oct 15 '24 14:10 TheFrenchGhosty

Same issue here; it does not happen every time but more than half of the attempts.

svezg avatar Oct 22 '24 18:10 svezg

Same issue here, for me it happens every time when using Quickfill (autofill works ok without Quickfill)

tibideky avatar Oct 26 '24 17:10 tibideky

Hello everyone, sorry for the long silence.

I can reproduce the issue. Apparently, AutoFill lifecycle has changed again, so the system now calls AutoFill methods in a different order than KeePassium expects. This had happened before and AutoFill is already a patchwork of conditional code that "mostly works" on iOS 15-18 and macOS 12-15. Fixing it with yet another patch would likely break things on older systems.

So our plan is to drop older systems, increasing the the minimum requirement to iOS 17 and macOS 14 (the ones we can actually test), then re-analyze the current AutoFill lifecycle, and rewire things accordingly. This is at the top of the queue, but might take some time to finish. Stay tuned!

keepassium avatar Nov 04 '24 22:11 keepassium

Just uploaded an update (1.54.156), please give it a try.

keepassium avatar Nov 28 '24 23:11 keepassium

Just uploaded an update (1.54.156), please give it a try.

Did some checking the past two days and it looks good; no hangups so far.

svezg avatar Nov 30 '24 22:11 svezg

Yes, I downloaded 1.54.156 via Testtflight, installed and seems to work well here again. The only one-time issue I encountered was that the application crashed only once right after installing and setting up / adding the database and turning on quick-autofill, at the first try of using quick-autofill. Since then, no crashes and quick-autofill works well and stable.

tibideky avatar Dec 01 '24 06:12 tibideky

It seems it is fixed completely (1.54.156, latest MacOS), but I still managed to get this bug here and then. Not always, but like 10% of the cases. I'll check better what I'm doing differently, so others can reproduce too.

matheusgomesms avatar Dec 12 '24 08:12 matheusgomesms

Ok, I guess we can consider this fixed. Should this happen again, please comment to reopen. (Preferably with steps to reproduce :)

keepassium avatar Jan 11 '25 09:01 keepassium