1Password addon not connecting to app on Edge Chromium
Is it expected that the addon fails to connect to 1Password when using the Chrome extension on the new Edge browser?
Edge Version 80.0.361.33 (Official build) Beta (64-bit)
1Password Version: 7.3.2
Extension Version: 4.7.5.90
OS Version: 10.15.2 (19C57)
Sync Type: 1Password Online
Comments
-
Edge support is only available in the Beta channel at this time, and requires copying the Chrome NativeMessageHosts json file into the corresponding path for Edge.
@rudy - do you mind describing the set of steps that I need to follow? I have the Beta, but I couldn't find the steps for NativeMessageHosts on the forum...
0 -
Ok, found how to do it, but now the extension icon just stays dimmed and doesn't actually fill in anything:
user@mac NativeMessagingHosts % pwd /Users/user/Library/Application Support/Google/Chrome/NativeMessagingHosts NativeMessagingHosts % cp 2bua8c4s2c.com.agilebits.1password.json ~/Library/Application\ Support/Microsoft\ Edge\ Beta/NativeMessagingHosts
0 -
I have the beta versions of both Edgium and 1Password
0 -
@ag_ana here's the version that I'm running:
1Password 7
Version 7.3.2 (70302004)
1Password Store
https://app-updates.agilebits.com/product_history/OPM7#v704030020 -
Ok, installed from the website instead of the Store version, and am now getting the right beta build. It's also working correctly with Edge, tho the extension icon is still greyed out.
1Password 7
Version 7.4.4.BETA-0 (70404000)
1Password Beta0 -
No worries. I'm wondering if it's a bug - it doesn't show up dark like that in other browsers.
0 -
It's not exactly a bug, @kop48, but more a Chrome quirk I suspect has been carried over to Edgium. Chrome doesn't invert extension icons quite like Firefox does so it makes them look like they're disabled when really they're just not inverting for the dark theme and are still a-okay. I see the same almost invisible icon in Brave on Windows, another Chromium-based browser. I suspect this is probably an issue across a number of them. Nothing we can do about it, sadly, but it should still work even though it looks a bit awkward.
0