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

Same issue here. MikeT's json file fix worked for me, but I'd just like to point out that I'm getting a little frustrated with recent updates to 1Password. I've had more issues with 1Password since updating to 8.x than in the previous 6 years of using the product. While all issues have so far been addressed eventually, it seems like a lot more bugs have been slipping past QA recently and quite frankly I do not believe v8 was ready for prime time when released. I've felt like I've been beta testing ever since installing it, and while I am sometimes OK with being an early adopter, I prefer to know that's the case beforehand. For a utility that's supposed to be mostly invisible to the user, it is unacceptable to be asking users to fix json typos and whatnot in (ostensibly) a non-beta product. It's shaken my faith in 1Password and I do plan to try out competitors for the first time ever when my contract comes up for renewal.

after restarting my machine the same issue kept coming back

@eastwest No one is stopping you, but LastPass has several breaches with stolen customer passwords. One recently if you missed out on the news.

Stopping me from what? Are you confusing me with someone?

Instead of manually updating the json file, one can do following terminal command for a quick fix (Chromium browsers, e.g. Google Chrome, Brave etc).
One could do same for Firefox by updating the json path with the one used by FF's extension.


sed -i '' s'/MacOS.MacOS/MacOS/' ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.1password.1password.json


then restart browser.

What the one-liner does is it would in-place update the specified file by replacing the MacOS/MacOS bit with MacOS. It does not have any effect on a working file.

Persistent Workaround?

All... please be guided by what the 1Password team says, as they are the authority, but I think I have found a simpler more persistent fix until a patched version appears.

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

This allows the pathname with the "double MacOS' in it to work and the fact that the config file gets overwritten by starting 1Password makes no difference.

I think you will find it is a more persistent fix to the problem until it is patched.

Instead of manually updating the json file, one can do following terminal command for a quick fix (Chromium browsers, e.g. Google Chrome, Brave etc).
One could do same for Firefox by updating the json path with the one used by FF's extension.

sed -i '' s'/MacOS.MacOS/MacOS/' ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.1password.1password.json
then restart browser.

What the one-liner does is it would in-place update the specified file by replacing the MacOS/MacOS bit with MacOS. It does not have any effect on a working file.

Thx! Solution from @mashuma worked for me.

Hi, Could you get Opera addon working again as before please... (integration with 1P App). Thank you

Solution from @metahome works for me. Thank you

I am seeing some red flags about your testing and bug smashing process.

Alas, I have to agree. To be clear, I don't have any of the hate I see from other users here for v8. It works well for me and I (mostly) like the UI. But how can a bug like this slip through your (hopefully existing) testers. Chrome is the most widely used browser. Shouldn't you have at least one guy doing nothing but testing new versions of 1P with Chrome? How could he or she not have noticed that the browser extension wouldn't unlock????