Temporarily removing Desktop App Integration
Comments
-
I'm new to this thread, and to the forum. This morning, I had to install the 1Password extension on a new browser; the first time I've had to do this in a while. I was surprised when it asked me to sign in through the browser, even though I was already signed in on the desktop app, and was used to always signing in through the desktop app (this is one of the things I really appreciated when I first switched to 1Password).
I eventually found that the functionality I was expecting is now in the "classic" extension. I'm glad this option is still available, and was happy to see that this functionality will be (re) added to the new extension. However, it seems a bit odd that the new extension is now the default, having not yet reached feature parity with the "classic" extension. It seems like this would fit better as an opt-in beta instead of the default option.
0 -
Heya @nikmolnar ππΌ
Welcome to the forum, we're happy to have you! π
I'm glad you were able to find the extension that fit what you were looking for. Both 1Password in the browser and the 1Password classic extension have their own benefits (one of those definitely being the unlock method). There's lots of helpful little things in the 1Password in the browser extension which can help as you fill your way through the internet, but if you want to wait until this feature is more widely released that's understandable.
If you have any questions, please feel free to reach out.
0 -
@nikmolnar I agree - renaming 1Password X and making it the default makes no sense until it can do what the "Classic" extension does, aka touch id.
0 -
Hi - Any updates on this it has been 7 months since TouchID was removed and over 4 months since it was originally planned to be returned.
0 -
Hi @netcam !
The latest news came from @dteare on March 9th. Actually the desktop integration came to the Linux version of the app and the extension. (https://1password.community/discussion/comment/591579/#Comment_591579)
0 -
Given that the details of this sort of integration (especially with something like TouchID) are likely to be platform- and even browser-specific, I can't see why the Linux release would be encouraging for Mac OS users.
1Password works great in Safari. Unfortunately, Safari's implementation of a single search/address bar is so bad that it's a deal breaker for me.
0 -
This content has been removed.
-
just posting here so i "presumably" get notifications surrounding news. chomping at the bit :)
0 -
If all you are interested in is notifications on a discussion, you can also mark it as favorite ;)
Great to hear that you are excited about this!
0 -
Hi! Apologies for piling onto this thread with more complaints. I understand that this feature was removed, and you're working on bringing it back. Fair enough. As a developer myself, I get it.
My problem is that it was quite a headache for me to figure this all out.
I downloaded 1Password for Chrome from the Chrome Web Store, while I downloaded the classic extension for Firefox from 1Password's website. I noticed that the new extension is better in every way except that the classic extension supports Touch ID, but I didn't know that this was because I was using different extensions. It took a fair amount of clicking, searching, reading threads on this website, and being dumbfounded by documentation pages that I didn't know were for the other browser extension type for me to figure that out.
So then, with my newfound knowledge, I installed the newer extension on Firefox and wondered: where did my Touch ID go?!?! After more clicking, more searching, more reading threads that I didn't know were outdated, I found that Touch ID was not supported in 1Password X unless I switch to Chrome, get the beta extension for Chrome, and install the beta version of the macOS application.
Here we go. Beta extension for Chrome. Beta application for macOS. My head hurts, but I did it, right? I can use Touch ID now?
More clicking, more searching, more reading threads that I didn't know were outdated, and I find that I need to actually enable Desktop App Integration in my settings for this to work. So then I go to settings, look for the option, and bang my head on the keyboard aggressively when I couldn't find it. Then and only then did I find this thread.
I understand the situation now, but this shouldn't have been so hard to figure out. In the meantime, extensions, website pages, and documentation need to be clearer about what extension you're working with, what the trade-offs are, and what information is applicable for your situation. Forum threads with outdated information should be prominently labelled if not removed.
If I wanted my password manager to give me headaches, I would've kept my money and stuck with LastPass.
0 -
Any updates on restoring TouchID to Chrome? It has now been 8 months since this feature was temporarily removed.
0 -
To quote from that almost two months old update:
"Itβs also temporary as weβll be rolling things out to Windows and Mac users in the coming months."
It's understandable that people are asking for some actual news, and being referred to that old update isn't really satisfying.
0 -
Hey everyone! ππΌ
I'm excited to share some news with you all, A better way to unlock π
0 -
O heck ya
0 -
Thanks for all your hard work on bringing back this feature. Definitely a welcomed return. Just a note, that the beta desktop client is also needed for TouchID support.
0 -
Awesome, thank you!
0 -
Awesomesauce! Thank you very much. Will be checking it out right away! :)
0 -
Just tested and it works as advertised. Thanks!
0 -
Great, works very nicely! I'm very happy :)
0 -
Thank you all for the kind words and for your patience so far :)
0 -
What a coincidence in timing π working great here! Thanks everyone π
0 -
Finally - thank you guys :)
0 -
Thanks, it's working correctly ... except with Edge Canary.. is it normal for now? (but that's really cool!!)
0 -
Hey @mcnahum ,
You might need to perform some of the steps outlined on this page to get things working in Canary: https://support.1password.com/could-not-connect/#what-you-should-do
0