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

1P_Tommy Yes, all good now.

BLD

Do you see 2.14.1 available? Can you let me know if it solves the trouble you experienced? I see it is available in Chrome and Safari. One of my colleagues is reporting 2.14.1 is available in Edge too.

1P_Tommy Could you folks considering pulling 1P for Safari 2.14.0 from the macOS App Store? I downgraded to 2.13.0 and would like to stop being pestered to upgrade to a version I know is broken.

from @pct196:

If your Safari shows no passwords because of this problem check out the linked forum post below. The 1Password folks sent me details on how to fix it.

https://1password.community/discussion/comment/693892/#Comment_693892

This procedure has remedied 1Password for Safari (without app integration - direct via web) for my setup. Thanks!

I did test re-enabling app integration to see if it works - but it puts 1Password for Safari back in a broken state. So to sum up, disabling integration, signing out, and signing back in to 1Password for Safari direct via web works - but enabling app integration breaks it entirely.

If your Safari shows no passwords because of this problem check out the linked forum post below. The 1Password folks sent me details on how to fix it.

https://1password.community/discussion/141845/unable-to-fill-into-safari-after-updating-to-macos-ventura#latest

I'm having the same issue as today (8/21). 1Password for Safari started acting weird a few days ago, didn't think anything of it. Today I started getting the Oops message, after I restarted may 2019 MacBook Pro. Turning off the shared lock state seems to be the fix for me.

Thanks @cschombu for the TimeMachine suggestion! Since this issue doesn't seem to have a quick fix, I also went to retrieve 2.13 from TimeMachine history, unpacked it, locked out the updates URL, deleted the installed 2.14, and "loaded unpacked" 2.13. Now it works again. I'm surprised @1Password hasn't rolled 2.14 update back, but maybe this problem only plagues a subset of the users for some reason.

The 2.14 problem was also exhibiting a strange behavior where it would work fine when I started work in the morning (my MacBook wasn't off, just screen off, sleeping), but then an hour or two later the error would return. Perhaps some buffer filled? Or perhaps some other program/extension/usage pattern interacted with it so that it would lock up again. Perhaps this is why the bug got past testing/QA, maybe it wasn't immediately visible when the release tests were being executed.

Since ag_tommy confirmed that the "1Password for Safari.app" 2.14 is broken, I simply went into MAC OS Time Machine and restored 2.13, restarted Safari, and now all is well again.

Assuming there is no issue using 2.13 until a fix is available?

Easy workaround...

I was able to get the extension to work once upon reboot, but it was no longer connected to the menubar item in that an unlock with the extension left the menubar 1P locked.

In addition, once Safari was closed and relaunched, the "Oops..." error reasserted itself and nothing worked :-/

Sigh...none of the options above have worked for me with Safari. I've tried disabling and also reinstalling...no joy 😥