Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
RMNL
3 years agoNew Contributor
Browser extension for (Brave, Chrome, Firefox) no longer integrates with 1Password app (no Touch ID)
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
- fssbobNew Contributor
Prior to the 8.9.14 update, I was able to autofill in Chrome as long as the 1Password application was open on my Mac. Starting with the 8.9.14 update, I have to use the 1Password icon in the browser regardless of the computer 1Password app being open. Was this an intentional change?
1Password Version: 8.9.14
Extension Version: 2.6.0
OS Version: macOS 13.2
Browser:_ Chrome
Referrer: forum-search:Need to use the browser 1Password icon - MikeT
1Password Team
Just a note; this workaround will last until either the Mac restarts or the app fully terminates and restart. This is because we rewrite the file on launch.
We'll get an update out as soon as possible.
- MikeT
1Password Team
Thanks for confirming and helping us with this; we're working on it as we speak.
- RMNLNew Contributor
🤦♂️ That worked indeed! I did not expect that. Thanks again for the help. Good luck fixing the issue with a fix!
- 1P_Tommy
Moderator
@carrotmercinary
Please see this topic. I will merge your post momentarily. https://1password.community/discussion/comment/673871/#Comment_673871
- Former Member
I see the following logs in the console, it looks like the Chrome extension is looking for 1password 7, but I have the 1password 8 desktop app installed. Here are the logs:
Desktop app port disconnected. Error: Specified native messaging host not found.
background.js:2 💫 Looking for desktop app com.1password.1password
background.js:2 📤 Sendingmessage to native core <3668032738>
background.js:2 Desktop app port disconnected. Error: Specified native messaging host not found.
background.js:2 💫 Looking for desktop app com.1password.1password7
background.js:2 📤 Sendingmessage to native core <1221626756>
background.js:2 Desktop app port disconnected. Error: Specified native messaging host not found.
background.js:2 💫 Looking for desktop app com.1password.1password
background.js:2 📤 Sendingmessage to native core <2185135024>
background.js:2 Desktop app port disconnected. Error: Specified native messaging host not found.
background.js:2 💫 Looking for desktop app com.1password.1password7
1Password Version: 1Password for Mac 8.9.14 (80914009)
Extension Version: 2.6.0
OS Version: MacOS 12.6.2
Browser:_ Chrome
Referrer: forum-search:Looking for desktop app com.1password.1password7 - RMNLNew Contributor
MikeT First of all thanks for the tip. This works for me on Chrome and Firefox. I can't find the
com.1password.1password.json
file for the Brave Browser. I looked at~/Library/Application Support/BraveSoftware/Brave-Browser/NativeMessagingHosts/
but could not find it. Any idea where I should look? - MikeT
1Password Team
Thank you, that helps validates our theory and we're looking into a permanent fix for this.
- wizard86pzOccasional Contributor
Hi MikeT,
yes, it works perfectly on Safari extension, v2.6.1.And yes, editing the path, it works perfectly. Checked only on Chrome browsers.