In 7.7.805 1Password stopped working with Edge
My 1Password on Windows was just updated to 7.7.805. Now, the main desktop app ignores my system default browser (Edge) and always invokes Chrome when I click "Open and fill". How do I fix this?
Also, I was using the browser extension in Edge. This is the one that is a sidecar to the desktop application, not the one that runs independently. It stopped working; clicking on the icon did nothing. I found it had been disabled, but re-enabling it did nothing. I also found there was a second 1Password extension installed. I removed both and reinstalled from the Store. Now it works, but it is a different extension, though the version seems to still be 1.24.2. The 7.7.805 release notes do talk about the minimum version required but don't really match my experience. I don't think you should automatically install updates that disable functionality, or at least you should warn users what has happened and what they need to do.
1Password Version: 7.7.805
Extension Version: 1.24.2
OS Version: Windows 10 2004
Sync Type: 1Password
Referrer: forum-search:edge
Comments
-
Hi @DerryK !
Now it works, but it is a different extension, though the version seems to still be 1.24.2.
Since Windows desktop version 7.7.805 you need to install version 2.0.0 of the 1Password in the browser extension to get both working together. But actually this version 2.0.0 is not available for Edge Chrome (https://microsoftedge.microsoft.com/addons/detail/1password-–-password-mana/dppgmdbiimibapkepcbdbmkaabgiofem?hl=en). 1Password is aware of this issue and hopefully the new version will be approved soon.
In the meantime you could use the 1Password classic extension (https://chrome.google.com/webstore/detail/1password-extension-deskt/aomjjhallfgjeglblehebfpbcfeobpgk). Here the Windows desktop app integration still is working.
0 -
Thanks, Denal. I was able to reinstall the classic extension version 4.7.5.90. I was confused by the fact that it comes from the Chrome store; I didn't have to encounter that previously because I did an automatic conversion from Chrome to Edge which took care of installing the extensions.
I've been very happy with the classic extension, and very UNhappy with the fact that the new extension did not have login integration with the desktop application. From the release notes it looks like that is fixed in 7.7.805/2.0.0, so I'll be looking forward to trying that out when it is available on Edge.
Also, the desktop application now does open a tab in Edge, though I don't understand what changed that would cause that to be fixed.
I still don't understand why any of this happened -- why I couldn't open a link in Edge, and why the classic extension stopped working on Edge but started working again when I reinstalled it. But I believe I am okay for now. Let me know if I am misunderstanding anything.
Derry
0 -
I've been very happy with the classic extension, and very UNhappy with the fact that the new extension did not have login integration with the desktop application. From the release notes it looks like that is fixed in 7.7.805/2.0.0, so I'll be looking forward to trying that out when it is available on Edge.
Indeed, the latest version added this integration :)
I still don't understand why any of this happened -- why I couldn't open a link in Edge, and why the classic extension stopped working on Edge but started working again when I reinstalled it.
Did you perhaps close and reopen Edge during any of this? I wonder if there was a pending Edge update that you installed along the way.
0 -
:+1: :)
0