On behalf of the team, you're welcome.
**UPDATE: ** Nevermind. It's early. I need more coffee. All is working.
I have 1Password for Windows (Current Edition, Beta enabled) and 1Password for Edge and Chrome enabled. I can't seem to figure out how to get the extension loaded into the Edge Chromium dev instance. Is it because I'm running the Canary build?
I'm fairly convinced I always need more coffee, @rwsmith_scf. Or I just want an excuse to drink more coffee. Either way, I hope you've now got a cup on your desk and I'm glad all is well. Enjoy the new Edge and if we can do anything more to help, you know where to find us.
@bundtkate I am enjoying the new Edge Chromium, and also more coffee, but it all can't help with me being eager to get 1P 7.4 for Windows.
Ha! We're eager for you to have it too, but only when it's ready.
What about Edge Chromium on Mac OS X?
It's a possibility. This discussion is about Windows though.
Just a warning that upgrading to Edge Dev 78.0.268.1 that just came out (10 September) makes the latest 1P app 7.3.712 beta fail. It was working ok just prior to the Edge update.
When Edge Dev is launched it complains that! with the warning:
The 1P extension button is blanked out and opens up a generic menu.
The logs contain the following:
Refusing helper connection from "C:\Program Files (x86)\Microsoft\Edge Dev\Application\msedge.exe", because of untrusted certificate.
I've just sent a set of diagnostics for another thread about the .712 upgrade problems.
It looks like ChromiEdge changed its code signature with that update, @wigster. I see the same issue myself after forcing an update just now. I have flagged this for our development team so that they're aware and can take a closer look.
Thanks for letting us know, too! I have so many browsers installed for testing, but I definitely don't use all of them often enough to notice these troubles right away so the heads up is much appreciated.
Browser connection refused ....
Version 78.0.268.1 (Official build) dev (64-bit)
@scottyjn can you check who signed your msedge.exe file and share with us?
Hey Sergey...I just received another update for Edge a minute or so ago.
Version 78.0.268.3 (Official build) dev (64-bit)
The issue is now resolved
Great, thanks for the quick update.
Maybe I'm just slow, but I had significant difficulty trying to figure out how to get either the Chrome extension or the 1Password X browser app working on the Microsoft Edge Chromium Beta (version 77 or 78). So I figured I'd give people a step-by-step. Hopefully this helps someone
Glad you're enjoying the beta! I find it's simpler to just go to https://1password.com/downloads/#browsers since that's "one-stop shopping" for everything 1Password. And once Edge is finished and there's an official way for us to offer 1Password for it, I am sure we will have a download link specifically for that as well. Cheers!
1Password team, Microsoft Chromium based Edge browser will finally ship Jan 15th 2020, when can we expect the 1Password Extension to be fully supported for the new Edge browser and officially available via the Edge Addon Store and not via the "Allow extensions from other stores" option? Thanks!
Yup we know. But we have no control over whether or not there's a submission process for Edge extensions in place before then. Regardless, 1Password works just fine in Edge already.
Just to be clear;
Both the 1Password desktop companion extension and 1Password X extensions work fine in Edge Chromium builds and will continue to do so in the stable releases in January.
The current Microsoft extension store is hand-curated by Microsoft, there is no official submission process yet for anyone to submit their extension to the store. Microsoft has said they're working on it but we have no timeframe on this and once they have this ready, we'll try to do it on day one.
We have reached out to Microsoft a few times in the past few months to get 1Password in but in the long run, we're just stuck waiting for this submission process.