As of today, my 1password extension for Brave, Chrome and Firefox no longer seems to connect to the 1Password app on my Mac. I now need to use my password instead of Touch ID for opening the extension and when you want to add a new item or edit an old item, the browser opens an edit window in another tab instead of opening an overlay through the 1password app. I'm also not automatically logged in when the 1Password app is already open and unlocked. I've tried to toggle both the "Integrate with 1Password app" setting in the browser as well as the "Connect with 1Password in the Browser" a couple of times, but that does not help. In Brave I reinstalled the extension as well. Again, no resolution. I can see that the 1Password helper is running in the Activity monitor. What has happened? What am I missing? I hope someone can help me or point me in the right direction. Thanks! 1Password Version: 8.9.14 (80914009) Extension Version: 2.6.0 OS Version: 13.1 (22C65) Browser:_ Brave v1.47.186

Each browser has to individually be signed into after recent update to activate 1Password application in browser. I had the same issue after the last update which was fixed. But it has happened again. My computer operates the most recent MacOS it can have, Catalina. 1Password Version: 8.9.14 Extension Version: 2.5.1 OS Version: 10.15.7 Browser:_ Firefox/Chrome Referrer: forum-search:After recent update, each browser needs to individually be signed in to 1Password.

I'm experience the same thing - Firefox on Mac. Help!

@rthiker Apologies for the trouble. The team is aware and working on a resolution. You should be able to unlock with your password while we investigate. Please let know if you experience otherwise.

Hi @rthiker, As Tommy mentioned, we're looking into it. For the moment, can you try the following to see if it will allow 1Password extension to unlock automatically in Chrome for you: Open Finder and select the Go menu > Go To Folder on top or press Command + Shift + G Copy and paste the following line: ~/Library/Application Support/Google/Chrome/NativeMessagingHosts Press enter to go there. You should see a file called com.1password.1password.json, open it with your text editor On the "path": line and at the far right, you can see two MacOS folders in the path, remove one of the MacOS folder and save it. You should have this saved instead: "path": "/Applications/1Password.app/Contents/Library/LoginItems/1Password Browser Helper.app/Contents/MacOS/1Password-BrowserSupport" Restart Chrome and 1Password extension should now unlock automatically with the main 1Password app. If that works, repeat the same for Firefox but this time in step 2, copy and paste this path: ~/Library/Application Support/Mozilla/NativeMessagingHosts. Note: This workaround will last until the app or the Mac restarts; the app will rewrite the file on the first launch. A full fix is coming very soon. I hope this helps for now. We'll get a new update out soon to fix this.

Same here, with 1Password 2.6.1 on Chrome Stable branch 109.0.5414.119 on macOS Ventura 13.2 (22D49), M1 chipset. The "tied" 1Password app is the PRODUCTION branch 8.9.14 (80914009).

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

bravouniform
New Contributor
3 years ago
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
1Password Team
3 years ago
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.
Former Member
3 years ago
I confirm. Issue solved on Chrome / Firefox and Brave on Mac.
Former Member
3 years ago
It appears that 8.9.15 has been released, and for me has resolved this issue in Edge on a Mac.
Don234
New Contributor
3 years ago
I am using Edge (latest version on my Mac) and metahome's fix worked. Thanks.
Former Member
3 years ago
In case anyone is using Vivaldi (Chrome based), the path to make MikeT changes is: .../Library/Application Support/Vivaldi/NativeMessagingHosts/.
djarsky
New Contributor
3 years ago

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
Enceladus
Occasional Contributor
3 years ago
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.
fuchsr
Occasional Contributor
3 years ago

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????
Former Member
3 years ago
Solution from metahome works for me. Thank you