MacOS, Safari extension - autofill issue

Just upgraded to Safari extension 2024.8.0. This version fixed many of the authentication issues I was experiencing this year.

However, now the keyboard shortcut for autofill is acting strangely.

Description of behavior:

  1. Load a login webpage
  2. Press CMD+Shift+L to autofill
  3. Username + Password does not autofill
  4. If I click the Bitwarden extension in the toolbar, THEN the Username + Password autofill

I’ve tried to reinstall the extension and this behavior persists.

Has anyone else experienced this?

6 Likes

Same issue here. Safari BW extension Autofill is set to “When field is selected (on focus)” and “User Names & Passwords” is un-checked in the Safari Settings. BW does not fill in my user name or passwords until I click in the Bitwarden menu. This used to work just fine with all the same settings.

Confirming the issue here. I hunted around for settings which may have been or might be changed, without success.

Bitwarden 2024.8.0 in Safari 17.6 under MacOS 14.6.1

1 Like

Check now guys, it was bugging out for me too and is now working properly. Seems to have been the server.

I just tried again. I cleared extension data and logged back in. I still need to click the extension icon in the toolbar for the autofill to work.

MacOS: 14.6.1
Safari: Version 17.6 (19618.3.11.11.5)
Bitwarden extension: Version: 2024.8.0

Yeah idk, it stopped working again for me too. It did work for a little while though.

Thank you for including all your version numbers.

I had upgraded to Sonoma 14.6.1 but that didn’t solve my issue with the extension not finding my vault entries. Then I realized I was one Bitwarden version behind (2024.7.0) as I’d not (to my recollection) received a notification of the new version. When I updated, my vault entries reappeared. I was ready to abandon Bitwarden for Proton Pass (and I may yet do so, but now no rush) if I could (can) successfully migrate my data.

Ex4kPeaker… I think you’re responding to the wrong thread.

Hoping the community can resolve the Safari autofill issue with 24.8.0. I’m happy to test, if needed.

Same issue here. No autofill prompt when field is selected, and the keyboard shortcut is not working. I’m on current Bitwarden release 2024.8.0, Safari 17.6, Sonoma 14.6.1.

Updated to latest extension 2024.8.1 and auto-fill is still not working on Safari Version 17.6 (19618.3.11.11.5), Sonoma 14.6.1 (23G93).

Confirming the same here.

Same here… autofill still not working in Safari after updating to 2024.8.1.

Same issue for me as well. Bitwarden Version: 2024.8.1, Sonoma 14.6.1

+1 for Bitwarden 2024.7.1, Sonoma 14.6.1, Safari 17.6.

Seems to happen quite often that new Safari extension version breaks existing features, e.g. Safari extension - allow window resize and autoscroll issue

Regression testing?

Before you ask, using Safari because it’s mainstream but safer and more private. Using Mac because it’s a solid, productive platform.

Edit: With Bitwarden 2024.8.1, autofill is now happening if you hit Cmd-Shift-L and then click on the Bitwarden extension icon. I kid you not.

Edit: With Bitwarden 2024.8.1, autofill is now happening if you hit Cmd-Shift-L and then click on the Bitwarden extension icon. I kid you not.

I noticed this with 2024.8.0 as well. Unfortunately, I didn’t notice whether the issue began with the 2024.8.0 Bitwarden update, or with the latest Safari update.

Same version(s) and same problem here :frowning:

Same here. Command-Shift-L does not autofill. If I immediately click the Bitwarden extension icon in the Safari toolbar right after trying the keyboard shortcut, then it autofills.

Mac OS 14.6.1, Safari 17,6, Bitwarden 2024.08.01

Skip the Cmd-Shift-L, just click on the extension icon and the correct login item which will be displayed. Works to add a TOTP as well.

Basically, at the moment I stick to mouse actions until it is fixed.

Same issue here. This is very annoying since as part of my work I have to authenticate frequently.

Safari: Version 17.6 (19618.3.11.11.5)
Bitwarden Extension: 2024.7.1

Same issue here. Just chiming in to bump and stay updated.

Has anyone here reported this as a bug yet? (I can’t figure out how to do that properly)