Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
Former Member
4 years agoFingerprint Unlock in Chrome doesn't work anymore
Hey,
I'm using a company license and the https://chrome.google.com/webstore/detail/1password-%E2%80%93-password-mana/aeblfdkhhhdcdjpifhhbdiojplfjncoa on a MacBook together with Brave as Browser (...
Former Member
3 years agoI've solved the issue, it's definitely the fault of the 1Password 8 desktop app for Mac OS. Took me like 5 minutes to figure it out after looking at the browser extension logs and googling the error messages.
TLDR if you want to fix it on your machine while you wait for an update just do the following:
Open the 1Password 8 (com.1password.1password) Chrome manifest.json file in a text or code editor (located at
~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.1password.1password.json
)
Change the value of the "path"
property to "/Applications/1Password.app/Contents/Library/LoginItems/1Password Browser Helper.app/Contents/MacOS/1Password-BrowserSupport"
.
Your com.1password.1password.json
file should then look like the following:
json
{
"name": "com.1password.1password",
"description": "1Password BrowserSupport",
"path": "/Applications/1Password.app/Contents/Library/LoginItems/1Password Browser Helper.app/Contents/MacOS/1Password-BrowserSupport",
"type": "stdio",
"allowed_origins": [
"chrome-extension://hjlinigoblmkhjejkmbegnoaljkphmgo/",
"chrome-extension://khgocmkkpikpnmmkgmdnfckapcdkgfaf/",
"chrome-extension://aeblfdkhhhdcdjpifhhbdiojplfjncoa/",
"chrome-extension://dppgmdbiimibapkepcbdbmkaabgiofem/"
]
}
The problem is the "path"
property has a typo in it, the one that was installed on my machine was
json
{
"name": "com.1password.1password",
"description": "1Password BrowserSupport",
"path": "/Applications/1Password.app/Contents/Library/LoginItems/1Password Browser Helper.app/Contents/MacOS/MacOS/1Password-BrowserSupport",
"type": "stdio",
"allowed_origins": [
"chrome-extension://hjlinigoblmkhjejkmbegnoaljkphmgo/",
"chrome-extension://khgocmkkpikpnmmkgmdnfckapcdkgfaf/",
"chrome-extension://aeblfdkhhhdcdjpifhhbdiojplfjncoa/",
"chrome-extension://dppgmdbiimibapkepcbdbmkaabgiofem/"
]
}
Note the "MacOS/MacOS" part of the path. If you actually go to that path using Show Package Contents in Finder you'll see that the real location of the BrowserSupport application is under "MacOS", not "MacOS/MacOS".
This took me literally 5 minutes to figure out and solve after looking at the browser extension console error log, noting the "Error: Specified native messaging host not found." error message, doing some quick googling, figuring it was probably a misconfigured manifest file, checking https://developer.chrome.com/docs/apps/nativeMessaging/ to see where the file lives, then checking it and the real path to see the discrepancy. It's taken more time for me to write this post then it did to diagnose & fix the issue on my machine.
Hope this helps everyone else that's been annoyed with this issue :)