keepassium / KeePassium

KeePass-compatible password manager for iOS
https://keepassium.com
Other
1.21k stars 103 forks source link

Autofill overlay doesn't work on macOS #230

Open rghedin opened 2 years ago

rghedin commented 2 years ago

Description When I summon the autofill screen on Safari, Keepassium overlay doesn't work. It appears, but I can't click on anything. I can't even dismiss the overlay — for that, I need to press Esc twice.

How to reproduce

  1. Go to a login form and select Keepassium;
  2. Kepassium overlay will open;
  3. Can't click on anything.

Expected behavior That buttons are clickable.

Screenshots https://user-images.githubusercontent.com/19216581/167126103-94e6534d-53b7-4751-81b3-022a703c1b7d.mov

Environment:

rghedin commented 2 years ago

An update.

I restarted Safari and the overlay is working fine again. Not sure what triggered it to became non-responsive, but I'll keep an eye on it.

keepassium commented 2 years ago

Thanks! Yeah, this happens sometimes, randomly (?) and I've been struggling to figure it out (or reproduce reliably). Interestingly, keyboard still works: you can close AutoFill by pressing Esc.

This was also reported on Reddit, and one of the comments suggested steps to reproduce:

I can reproduce it every time. this usually happens on MacBook Pro M1Pro after Safari is idle for some time. i think after the Mac goes to slip and the lid is closed.

In your case, does the issue also happen after the Mac wakes from sleep?

rghedin commented 2 years ago

In your case, does the issue also happen after the Mac wakes from sleep?

I left my MacBook Pro (Intel-based) asleep last night. Just tested in the morning and it's still working fine, so, no, sleeping probably isn't the cause.

I saw a related issue that may have de same root: sometimes, LinkedIn website just stop opening. When I try loading it, it hangs eternally in a blank page, and only got back if I fully close and reopen Safari — the same solution I found for Keepassium's issue.

keepassium commented 2 years ago

Thanks for testing! So the mystery remains…

At the moment I can offer only a slightly faster workaround: can terminate "KeePassium AutoFill (Safari)" process via Activity Monitor, no need to restart Safari.

adlpz commented 1 year ago

Posting here to confirm that as of today this issue remains. My workaround is keeping a bash script handy that kills Keepassium whenever this happens.

Is there anything we can provide you to make debugging easier?

Happy paying customer by the way, thanks for the amazing app :)

keepassium commented 1 year ago

My workaround is keeping a bash script handy that kills Keepassium whenever this happens.

@adlpz, thank you! Making an app that people use is one thing. Making an app that people create-workarounds-to-use-despite-its-bugs feels like an accomplishment, oddly enough :)

Is there anything we can provide you to make debugging easier?

A reliable way to reproduce the issue would help tremendously. Without it, I need to test every hypothesis for a week only to have a probabilistic answer in the end ("maybe solved" or "definitely remains"). Which is so inefficient that I don't really want to go that path…

keepassium commented 1 year ago

I was poking around trying to reproduce the issue, and it just happened — randomly, though :) But there are some potentially useful nuggets:

Can anyone test/confirm the last one, please?

adlpz commented 1 year ago

@keepassium I can confirm, last time it froze I disconnected the external display (on a Macbook Air M1) and it became responsive again.

Tried moving it between screens. Did not solve the issue.

After that, even if the display is plugged back in, the app functions normally, until it freezes again.

keepassium commented 1 year ago

After upgrading to 13.2.1 a couple of weeks ago, I have not encountered this issue at all, not once. Is it just me?

adlpz commented 1 year ago

@keepassium I was on the same boat, no issues for a while, but it just happened again! And, as before, I disconnected the external display on my Macbook and worked again.

So, it's still there :(

keepassium commented 1 year ago

@adlpz, thanks! And I was just about to close the issue… :)

On the positive side, it got better. Moreover, it got better without any changes in KeePassium — which supports the hypothesis that this is a system issue.

keepassium commented 1 year ago

Has anyone encountered this on macOS 14 Sonoma?