Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
ChrisJenkins
9 days agoFrequent Contributor
macOS: After Updating to 1Password for Safari 8.12.4 autofill for many sites no longer works
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,...
- 5 hours ago
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:- Your version of macOS: Find out which macOS your Mac is using
- The address of the website where filling isn't working.
- Which specific field isn't being filled.
-Dave
Squuiid
2 days agoNew Member
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_Doctor2 days agoOccasional Contributor
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