Forum Discussion
Safari Extension and Touch ID no longer play together
Ahoy! Yes, I did search this topic, found some similar threads, but I didn't see a resolution that will work for me.
Problem: I use 1P 8.9.15 and Safari on macOS Ventura. The 1P extension is now requiring I use the password after the app time limit which I think I have set for 1 hour. (Meaning, 1P is supposed to accept Touch ID after that hour at the very least.) Then when the 1Password app itself is unlocked. This was working fine until just recently, like, within the last day. What could have gone wrong? What do I need to do to get back to the behavior before, meaning, I can use Touch ID with the Safari extension. I haven't fiddled with any of the preferences of the app or the laptop.
thanks!
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser:_ Not Provided
19 Replies
- 1P_Tommy
Moderator
Hey @AndyQ
It's here. Someone will be with you as soon as possible.
ref: QUZ-26569-169
- Former Member
I have the same issue but on Sonoma (beta 4) and nightly - looks like the browser extension just won't communicate with the app at all. Touch ID not working in browser, and if I unlock app, browser remains locked, and vice versa.
(support request filed but as yet no support ID number received)
- 1P_Tommy
Moderator
Thanks Geoff.
ref: LEN-41163-177
- Former Member
Thanks for you help. I have followed these instructions and the support ID is
[#LEN-41163-177]Geoff
- 1P_Tommy
Moderator
Hey @GeoffMather
Let's get you over to email support were we can look at diagnostic reports from the device and see if we can get you in a better place. I'd like to ask you to create a diagnostics report from your device:
- Open 1Password.
- Press command and comma. The 1Password settings (preferences) will open.
- Tap Advanced.
- Click Send Diagnostics.
- Click Reveal to locate the report in your downloads folder.
Attach the diagnostics to an email message addressed to
support+forum@1password.com
.- Your forum username:
GeoffMather
A link to this thread:
https://1password.community/discussion/comment/692127/#Comment_692127
Please do not post your diagnostic report to the forum. This is for your privacy and security.
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!
- Former Member
Are you experts willing to revisit this issue? It once worked for me that signing into 1Password via the icon in Safari would give me a pop up window with a finger print and accept touch ID. Now that is doesn't work, I miss it. I carefully followed the process suggested by ag_tommy and it doesn't work for me. Because it once worked, should I suspect some problem in a plist somewhere and delete that file?
But first Q: Is this still supposed to work now or did something change?
I have a MacBookPro 16" with M1 chip running Ventura 13.5 And 1Password is 8.10.8
with 1Password for Safari being 2.13.0
I have tried deleting 1Pwd for Safari and reinstalling, but that just brings it back from the cloud which might not really be a fresh copy. Are there other things I can try? or just wait for the next round of updates?Geoff Mather
- 1P_Dave
Moderator
@josmac
I'm happy to hear that Tommy's instructions helped and that everything is working again. 🙂
-Dave
- Former Member
Just a note, I too experienced this problem. It cropped up with the last update to the Safari extension. The solution 1P_Tommy provided worked for me. Thanks!
Joseph
- 1P_Dave
Moderator
@kevbob
Thank you for the additional information. We'll keep an eye out for further reports of the issue. 🙂
-Dave
- Former Member
Andrew, yesterday I confirmed it was resolved. My followup was in response to Dave mentioning closing and reopening the browser reestablished a connection. I explained, I did do those things already when it was not working and that did not help. The only thing that worked was that my 1P for Safari extension app got an update. I was just curious what might have gone wrong, but it's all conjecture, I realize. Again, this is no longer an issue, I was just providing my additional context to what made it work (when it should probably not have broken at all). That's it- this probably has no real answer, I get that- software glitches are ephemeral.