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 (basically Chrome). I noticed the following issues recently (since about a week):
- When I unlock the Mac App, the Browser Extension is still locked
- When I want to unlock the Browser extension, it always asks for my password. This is annoying since it is very long and I prefer to use my fingerprint.
- The little hint that appears on input fields now does nothing when clicked. It forces you to use the keyboard shortcut. Why?? Why not just open the extension when I click on the icon?
- The Mac App keeps suggesting that I download the extension, even though I have it installed
The same thing happens in Chrome. I think an update broke something because everything worked very smoothly before. I also tried uninstalling and re-installing the browser extension.
A fix is highly appreciated since this is very annoying.
Thanks
1Password Version: 1Password 7 Version 7.9.3 (70903004) Mac App Store
Extension Version: 2.3.0
OS Version: macOS 12.2.1 (21D62)
49 Replies
- Former Member
Thank you so much for this. I was just getting frustrated and found this solution that works perfectly. I am using Firefox so my manifest was in a different location but required the same fix.
~/Library/Application Support/Mozilla/NativeMessagingHosts/com.1password.1password.json
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_extensions": [
"{0a75d802-9aed-41e7-8daa-24c067386e82}",
"{25fc87fa-4d31-4fee-b5c1-c32a7844c063}",
"{d634138d-c276-4fc8-924b-40a0ea21d284}"
]
}
- Former Member
I'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 wasjson
{
"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 :)
- Former Member
I expect the same behavior in Crome and Firefoxe since some days.
- Former Member
I started getting this issue yesterday. It was working fine until then. I had just upgraded from macOS 13.1 to 13.2 (smoking gun?)
Now both Safari and Firefox browsers ask for the full password to open 1P with no option to use Touch ID. - Former Member
Same issue here. Tried the "disable Integrate with 1Password, restart etc." turnaround described above, but still the same: 1Password app (macOS) is unlocked, but I nevertheless every time need to also unlock the browser extension and on doing so have to enter the passphrase - no fingerprint option offered.
- Former Member
I'm having the same issues as well. I've followed all the instructions on this thread, but no luck.
- steph_giles
1Password Team
Hey @goldylox,
I'm sorry for the trouble, thanks for sharing the support ID we can continue to investigate there.
- Former Member
I am having the same issue. Have tried everything above. Has there been a solution? This is extremely frustrating. I have to manually log in anytime I open and close the browser and it quite honestly makes the product almost not worth using. Thank you.
EDIT -
Here is my support ID: [#PTF-44499-252]
- Former Member
Hey @harieshokunin, I'm sorry that you've run into this issue. We would be more than happy to help.
At this time, I'd like you to reproduce the issue and then send over the following so we can take a closer look at what may be going on:
- The extension console log: https://support.1password.com/cs/extension-console-log/
- A diagnostics report: https://support.1password.com/diagnostics/
Attach the logs and diagnostics to an email message addressed to mailto:support+forum@1password.com.
With your email please include:
* A link to this thread: https://1password.community/discussion/128098/fingerprint-unlock-in-chrome-doesnt-work-anymore#latest
* Your forum username: harieshokuninYou should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks!
- Former Member
Hello, I am having a very difficult time with the 1Password touch id in the chrome extention as well as everyone else!
Disable [Integrate with 1Password app]
Delete and reinstall chrome extention
I have done these steps above, but the problem persists.Spec.
* 1Password for Mac 8.9.8 (80908009)
* Google Chrome version 107.0.5304.110 (official build) (arm64)
* Chrome extension: 2.4.1I am going to send for "mailto:support+forum@1password.com"
Can you solve the problem?
Translated with http://www.DeepL.com/Translator (free version)