1Password for Safari isn't working on macOS 14.2 BETA

Hey @jdawgnoonan,

I can confirm that there is a known bug with the macOS 14.2 beta that's affecting 1Password for Safari. The bug has been identified, and the fix should be available in a future macOS update.

In the meantime, can you let us know if the behaviour improves after clearing Safari's history? Here's how you can do that:

1 Open Safari.
2 Click "History" in the macOS menu bar and select "Clear History" to clear all history.
3 Once that's done, restart Safari by clicking Safari > Quit Safari and relaunching Safari.

Let us know how you get on!

Hello @steph_giles, yes, that did fix the issue! Thank you!

It fixed it for me briefly but a few days later we are back to the same behaviour. There is clearly something not working right here and a fix is needed?

I just tried this and it worked! Hoping it sticks.

@jdawgnoonan, @strickers, and @mmcwatters

I'm happy to hear that the steps posted by Steph helped. If the issue does occur again then you'll need to go through those steps again.

As mentioned, this is an issue with Safari in the macOS beta and hopefully a fix will be released in a future macOS beta update.

-Dave

ref: dev/core/core#25725

Hello @Fresco, @olson, @mmcwatters, and @arrtz3! 👋

I'm sorry that 1Password for Safari isn't working on your Mac. Are you all running a beta version of macOS Sonoma? If you are then there's a known issue in Safari that is causing the symptoms mentioned, we hope to see a fix included in a future beta for macOS Sonoma.

For the time being, please try these steps:

1 Open Safari.
2 Click "History" in the macOS menu bar and select "Clear History" to clear all history.
3 Once that's done, restart Safari by clicking Safari > Quit Safari. Then re-open Safari.

Let me know if that doesn't work.

-Dave

ref: dev/core/core#25725

Clearing History seemed to fix the problem.

Yes. Clearing the history works.

I'm glad that clearing history helped. Hopefully a future macOS beta will include a permanent fix soon.

-Dave

The MacOS 14.2 beta 2 (23C5041e) appears to have fixed the issues with the extension.