Browser extension for (Brave, Chrome, Firefox) no longer integrates with 1Password app (no Touch ID)

Happy to say @MikeT 's temp fix removing the extra MacOS/ in the JSON path works perfectly, and I can confirm the problem doesn't affect Safari. I do hope this can be actually fixed soon though — I had a couple family members (whom I just moved over from LastPass) already getting confused by this. It makes a poor impression when they see a bug so soon after starting to use 1Password. I understand as a developer and sysadmin that this is just a little typo in a config file and doesn't reflect on the overall stability or security of 1P, but those distinctions are lost on less technical folks.

It does seem like auto-unlock should be included in an acceptance test somewhere in the extension build pipeline.

I just opened a terminal window, went to /Applications/1Password.app/Contents/Library/LoginItems/1Password Browser Helper.app/Contents/MacOS

cd /Applications/1Password.app/Contents/Library/LoginItems/1Password\ Browser\ Helper.app/Contents/MacOS

then I created a symbolic link:

ln -s . MacOS
https://1password.community/discussion/comment/674190#Comment_674190

Thank you, @metahome! This worked perfectly!

-David

In case anyone is using Vivaldi (Chrome based), the path to make @MikeT changes is: .../Library/Application Support/Vivaldi/NativeMessagingHosts/.

I am using Edge (latest version on my Mac) and metahome's fix worked. Thanks.

It appears that 8.9.15 has been released, and for me has resolved this issue in Edge on a Mac.

I confirm. Issue solved on Chrome / Firefox and Brave on Mac.

Hi folks,

Apologies for not getting back to you sooner, we were working on this all weekend. As some of you have noticed, we just shipped the 1Password for Mac 8.9.15 build to fix this issue. (Windows and Linux versions were not affected).

We shipped a quick fix on the nightly channel a few hours of this report on Saturday afternoon and then we wanted to triple check nothing else was affected before we ship the final and tested fix on the stable channel.

We have added more steps to our QA workflow to prevent this from happening again.

FWIW, this fixes the issue in Firefox, but I am still having the issue in Safari Technology Preview (not a big deal as it's not my daily driver, but wanted to report in case that is related to any additional issues).

@MikeT macOS 1P version 8.9.15 fixed the issue for me on both Firefox and Chrome browsers. Safari continues to work as before.

Thanks for the quick response!

The solution from @MikeT seems to work for me so far, going into the com.1password.1password.json file and deleting the redundant /MacOS folder reference in the path line /Applications/1Password.app/Contents/Library/LoginItems/1Password Browser Helper.app/Contents/MacOS/1Password-BrowserSupport.