Safari, Chrome etc. Extension 2.14.0 Broken - Edited title.

Turning the extension off, then on again, seems to have fixed it for me. I tried this yesterday (and it didn't help then), so I'm guessing some kind of potential temp fix has been already applied so that reinitializing the connection helps. Thanks!

I never had any issues with 2.14.0 in Chrome or Firefox, just Safari. And the workaround of turning off the shared lock state worked to get 2.14.0 working with Safari too.

1P Folks: Can you please add a giant note that shows up at the top of the macOS App Store release notes to remind us to turn shared lock state back on with the next release?

P.S. Is there a way to bookmark a specific post in this forum?

having bunch of issue with this new version as well

None of the support troubleshooting steps helped.
Very upsetting that 1password would release such a buggy production version.

Since upgrading 1Password for Safari to version 2.14.0 and Ventura to 13.5.1, I'm unable to use Touch ID or Apple Watch to unlock 1Password in Safari. They work in other browsers, and I can use them to unlock the 1Password app itself (as well as the Macs themselves), but in Safari I have to type the master password in full to unlock 1Password. This happens on an Apple M2 Pro Mac mini and a 16" M1 MacBook Pro.

1Password Version: 8.10.9
Extension Version: 2.14.0
OS Version: Ventura 13.5.1
Browser: Safari 16.6

I contacted 1Password support and they suggested the following that worked for me:

1. Right-click the 1Password icon in your browser's toolbar and click "Settings".
2. In the "General" section, turn off "Integrate with 1Password app".
3. Click the 1Password icon in your browser's toolbar.
4. Follow the on-screen prompts to unlock 1Password in the browser.

I don't know what "Integrate with 1Password app" does, but I'm not sure I need it.

Okay, I found a discussion of this on the Beta and Prerelease board (for some reason): https://1password.community/discussion/141777/safari-extension-2-14-0-broken

So you can close this.

I've merged it in @greenpig :)

To follow up, I had success by combining the methods described here.

1. Browser-bar icon -> Settings -> General -> turn off "integrate with 1Password app"
2. Quit Safari and quit 1Password
3. Reopen Safari. Browser-bar icon -> Manage Extension -> turn off the extension. Quit Safari.
4. Reopen Safari. Settings -> Extensions, and turn it back on.
5. Repeat #1 and this time turn integration back on.

I'm not sure if it was really necessary to quit and reopen all the apps, but this reestablished biometrics on both my computers.

I've tried all of the aforementioned solutions but 1Password for Safari 2.14.0 just hangs, returning the same oops error page with two buttons to reload or contact support. I also noticed that when I disable integration from the Settings page (to attempt app-less usage), the extension's vault authentication page does load, so I enter my vault password and it just hangs. The extension's background console shows the same two errors as when integration is enabled:


[Error] 15:04:10.531UnknownError: Cannot inject key into script value
i (background.js:2:2394192)
[Error] 15:04:10.576Unhandled Promise Rejection: AbortError: IDBTransaction will abort due to uncaught exception in an event handler
o (background.js:2:2393731)


FWIW, I did a little tracing of the errors and there appears to be some kind of type error which bubbles up as an unhandled exception error:

@sbauer I simply removed the 2.14.0 copy of 1Password for Safari from the Applications folder and then moved the 2.13.0 one into its place -- macOS prompted for the usual administrative authentication, of course. But the second half of the instructions that @1P_Tommy posted above for 2.14.0 also worked for me.