Skip to main content
February 28, 2026
Solved

macOS: After Updating to 1Password for Safari 8.12.4 autofill for many sites no longer works

  • February 28, 2026
  • 19 replies
  • 1492 views

Including 1Password Communities! This seems like a major faux-pas (everything was working fine before the update). Autofill still works on some sites.

macSO 26.3 with Safari 26.3. 1Password 8.12.5, 1Password for Safari 8.12.4.

Best answer by 1P_Dave

Hello folks, 

We've just released a new update for Safari which resolves an a known issue that would prevent autofill from working properly on certain websites. Please update 1Password for Safari to version 8.12.5


Thank you for your patience while we worked to release a fix for the autofill issue. If you're still seeing autofill issues after updating then please open a new discussion here and include the following: 


-Dave

19 replies

johnnygoodface
March 4, 2026

Starting a few days ago, either on Safari or Firefox, when I click on a field (for example when login at the bank), I can see the choices available (for example loginuser1, or loginuser2, etc.) but when I click on any of those choices, 1Password doesn't fill the fields. This happens ONLY on certain site, NOT ALL, only 20% approximatively. Never had any issues before

 

March 4, 2026

I'm having the same issue. Startred a few days ago. Same for me only some sites.

johnnygoodface
March 5, 2026

I concur that Chrome doesn't seem to be impacted here also

March 5, 2026

I don´t understand why this issue is marked as solved - it isn´t in the current available production version. I don´t want to go for a beta as productive system for a commercial password manager. That´s not what I expect to pay for. The workarounds with Universal Autofill are also not working for me.

Please get this resolved as soon as possible - thanks.

1P_Dave
1Password Employee
March 5, 2026

@cp7137 

Our team is working to release the fix as soon as possible, I'm sorry for the inconvenience. Marking a post as a solution to a thread doesn't mean that the issue/request itself is fixed or closed. It's a way to highlight the most up-to-date answer for anyone who stumbles onto the thread in the future.  

-Dave

March 5, 2026

Although still having the same issue on 8.12.4, it does seem to work if you refresh the login page and try again.

The_Doctor
March 5, 2026

Unfortunately, that approach does not work me, although I imagine it could work for some select pages.

March 7, 2026

@1P_Dave You have so many App Store 1-star reviews for the Safari extension over the past entire year that I've lost count. The extension DOES NOT WORK RELIABLY and AND THIS IS A RECURRING ISSUE. A hotfix is not enough, you need to re-write from scratch. As an IT professional I no longer recommend your product in a Mac environment due to the terrible user experience that you seemingly have zero interest in fixing. Look at your App Store reviews for crying out loud!

The_Doctor
March 7, 2026

@Squuiid and@1P_Dave 

I’ve been a 1Password user since V1.0, and still believe it is the best solution out there.  Browser integration and overall operating system integration have always been moving targets, so I tend to give a little grace when these issues crop up.

So, it’s not the fact that this bug exists, or made it through testing, that is frustrating to me.  Unless the fix requires a wholesale rewrite, the time to resolution is what I find frustrating.  If a longer and more expansive fix is required, per your comment above, then clear communication of a timeline would be helpful.

It is also unfortunate, that this lingering defect is juxtaposed with a pricing increase that ostensibly should mean more resources available to fix such issues. 

There is certainly a significant amount of inertia associated with long time users like myself which inoculate to some degree from switching to another password solution, especially one embedded in macOS.  That said, relying too much on that inertia is unwise.

I remain a supporter of the product, but would like better communication on this issue  

March 7, 2026

I too am having the same issues with the 1Password Safari extension (8.12.5) on  Safari  (26.3.1) on MacOS (Tahoe 26.3.1). I tried all of the recommended fixes none have worked. However, 1Password appears to work fine in Chrome, Firefox, and Edge on the same computer. 

While it may be unrelated, I have noticed that if I open up the 1P Safari extension on a website it does not always recognize the website even though if I click in the username or password windows I get the correct pop up options which don't work. 

March 8, 2026

The list does show up, but tapping it (no matter how many times) doesn't autofill the passwords.

This has been around at least 2-3 days now.

Reproducible in
- iPhone, iOS 26.2.1, 1Password for iOS 8.12.5 (81205001)

- iPad as well, iPadOS 26.3. Not with me now so don't have the 1Password version info. 

cyber-bacon
March 8, 2026

I can confirm the same issue for several days on macOS 26.3.1 with the latest 1Password version running (1Password for Mac 8.12.5 (81205001)), possibly starting after updating to 26.3.1 on March 4th. The list shows up, but clicking the item does not auto-fill — I have to copy/paste the credentials.

Auto-fill on iPadOS 26.3 has been working fine (except on the 1Password Community site) and seems okay on iOS 26.3.1 (1Password v8.12.5).

March 9, 2026

After a recent "update" from 1Password (browser extension 8.12.4.46 on MacOS Safari), it has moved the icon in the browser to the left of the URL address window and introduced a number of problems. Websites that were fine before no longer function. I have to switch back and forth and copy/paste passwords most of the time.

Now for the larger issue - support. Where is a tech support phone number? I get it that the company is saving money and being more efficient but I opened a support ticket (#ZXI-54789-543) online seven days ago and have yet to hear back after multiple follow-up attempts. It would be nice to have the option to call tech support if we need to. The problem with online only tech support is exactly what I'm experiencing with this paid product. I have been in the IT industry for many years and this has to be up there with the worst support around - this isn't my first support case with 1Password. 

It seems that they change and update the product and break things repeatedly. I want a password manager that works and doesn't require me to manually jump through hoops to do what it should automatically fill. 

March 9, 2026

For reference, I have the 1Password app showing 8.12.5. The browser extension for Safari still shows 8.12.4.46. The extension says that it will automatically update to the latest version if you restart the browser - not quite. I have restarted the browser twice, rebooted the iMac and still no update. What's interesting is that the release notes for 8.12.5 shows the following info. How exactly do they keep breaking things with updates? Is there no regression testing? This is basic stuff folks. Even the update process is broken here on the extension.

This is a Safari-only release.

  • We’ve fixed an issue that would prevent Autofill from working properly on many websites." 
March 9, 2026

I just uninstalled 1Password Safari Browser extension 8.12.4.46 and re-downloaded it.  It pulled 8.12.5.2 and while on the same login screen that was failing, immediately auto-filled successfully.  Limited sample set for testing, but certainly looks better.  I suggest uninstalling the extension (move extension to the trash in finder) and re-installing in Safari.  I didn't even close Safari and it worked right away.  Perhaps the updated version is now in production?

1P_Dave
1P_DaveAnswer
1Password Employee
March 9, 2026

Hello folks, 

We've just released a new update for Safari which resolves an a known issue that would prevent autofill from working properly on certain websites. Please update 1Password for Safari to version 8.12.5


Thank you for your patience while we worked to release a fix for the autofill issue. If you're still seeing autofill issues after updating then please open a new discussion here and include the following: 


-Dave