Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quick Auto Fill fills nothing on macOS #259

Open
baobao1270 opened this issue Oct 3, 2022 · 11 comments
Open

Quick Auto Fill fills nothing on macOS #259

baobao1270 opened this issue Oct 3, 2022 · 11 comments
Labels
bug Something isn't working

Comments

@baobao1270
Copy link

Description
The quick fill does now work on macOS. The quick fill window shows, but when the TouchID is pressed, nothing is filled.

2022-10-03.03.35.57.mov

How to reproduce
Steps to reproduce the behavior:

  1. Download KeePassium on MacOS
  2. Open any website and setup quick auto fill
  3. Reboot the macOS, than repeat step 2
  4. See error

Expected behavior
The KeePassium works like the iCloud Password Manager

Below is the screen recording of what iCloud Password Manager works like

2022-10-03.03.45.45.mov

Environment:

  • Device: MacBook Air M2 2022
  • OS: macOS 12.6
  • App Version: 1.36
@baobao1270 baobao1270 added the bug Something isn't working label Oct 3, 2022
@keepassium
Copy link
Owner

Thanks! It looks like AutoFill might be running out of memory (AutoFill memory limits).

Does it work if you click "KeePassium…" below the suggested account?

@baobao1270
Copy link
Author

Hi,

I think this might not caused by memory limit. The same database and same version of KeePassium works correctly on my iPad and iPhone. Only the on macOS can reproduce the problem.

The KeePassium in the suggested account list works.

I found when I turn the AppLock off, the quick autofill works again.

@moenodedev
Copy link

I also have to click "KeePassium..." in order to get AutoFill to work. After Touch ID the fields are filled. The database has only a few entries and they contain username, password, email, url, and otp fields.

@keepassium
Copy link
Owner

Thanks for the feedback! Can you please check if the issue persists in the latest 1.37.118? (it should be both in TestFlight and App Store now.)

@moenodedev
Copy link

Yes it still happens on 1.37.118.

@cryptosteve2
Copy link

cryptosteve2 commented May 4, 2023

Same here with Keepassium v1.42.129 Pro
Suggested autofill entry does not do anything, choosing "Keepassium Pro ..." works as expected.

Edit: doesn't work with strongbox too (see bug report 695 there). Seems to be a macOS regression.

@keepassium
Copy link
Owner

@cryptosteve2 , thanks!

@meckie-meck
Copy link

I encounter the same problem with KP 1.44.134 on macOS 13.4 on a MacBook Pro 14 2023. But it works on iOS and iPadOS.

@blinskey
Copy link

blinskey commented Sep 27, 2023

This bug is now fixed for me after upgrading to macOS Sonoma 14.0, but there is a new problem during the autofill process: a "KeePassium AutoFill" dialog is displayed after the autofill successfully executes. Sorry if this would be more appropriate for a new issue, but I figured I should note it here since it may be related to the previously buggy behavior.

Here's the exact sequence of events I'm seeing:

  1. When a login field is in focus, the macOS autofill prompt is displayed.
  2. I authenticate using TouchID.
  3. The login fields are correctly auto-filled and the form is submitted.
  4. A TouchID dialog is displayed, with the message "KeePassium AutoFill is trying to Unlock KeePassium." This persists until I authenticate again with TouchID to dismiss the dialog.

I'd be happy to provide video or the details of my configuration if that would be helpful. One thing that might be noteworthy is that I've enabled auto-fill for KeePassium but not iCloud Keychain in the macOS settings. That wasn't possible in macOS 13.

@keepassium
Copy link
Owner

@blinskey, thank you for the feedback!

It looks like the lifecycle of AutoFill process has changed on Sonoma. There are several reports that indicate the AutoFill keeps running in background, although the system is supposed to terminate it between the invocations. As a result, strange things happen. I will look into this.

@ezamelczyk
Copy link

@keepassium yeah it seems autofill in general is busted on sonoma. Passwords section in system settings does not pick up any passwords from external providers. I tested keepassium and 1password and both provide nothing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

7 participants