Latest Chrome Extension breaks Google Sign-In on our website?

And to be clear -- the error isn't happening when trying to use 1Password to sign in. The fact that it's enabled blocks the login attempt.

We're seeing the same issue with a web app that uses Google Sign In for Web and similar console errors about requests being blocked by the client.

I have been able to verify that upgrading the browser extension from v2.9.0 to 2.10.0 triggers the issue. Disabling the 1Password extension resolves the issue and no errors in the console.

We had the same issue. After widespread reports of google auth breaking for admin users of our web app (which is a requirement to access the admin dashboard features), we tracked down the problem to the 1password update. The solution was to temporarily disable 1password until authentication succeeded.

A few of our users have also reported that disabling 1Password SSO/federated login support does not resolve the issue either and the extension itself has to be completely disabled.

Hey @nicedawg, @jzebra, @cvanes,

I'm sorry for the trouble, I'd like to investigate this further. Could you provide me with a look to an example that I could access to do some testing?

In addition, can you confirm if you are using the beta version of 1Password in the browser or the latest stable release?

You can find this information if you right click the 1Password icon in your browser toolbar and choose Settings and then scroll right to the bottom.

Thanks in advance!

That is correct, and I'm also facing the same issue. I disabled the 1password extension on ms edge, and Google sign-in is working again.

1Password Extension version 2.10.0 is blocking the direct request from the browser because 1password can sign you in via OAuth, blocking the actual behaviour and then giving us a popup to save that OAuth sign.

That confirms an issue with the extension that blocks the Google request.

Don't they test their software?

@steph_giles happy to share a link to an app we're having issues with if you can DM me?

Can also confirm we are using the latest stable 2.10.0 release and verified this was not an issue in 2.9.0 before upgrading on my machine.

Thanks, @steph_giles ! Our site is https://www.vecteezy.com. To recreate the problem:
* make sure the 1Password chrome extension is enabled
* Click "Log In" at the top right
* Click "Log In with Google"
* Observe "Logging in..." hanging forever, and console shows aforementioned errors

And here's confirming I"m using the stable version
```
1Password in the browser 2.10.0

20246, on STABLE channel
```

Hey @nicedawg, @jzebra, @cvanes, @syedadeel2,

Thanks for getting back to me

It looks like you may be impacted by a newly added feature to the latest 1Password in the browser extension (version 2.10.0) that is designed to prevent competing sign-in popups but was enabled by default. Could you try the following:

1. Right click on the 1Password icon in your browser and select Settings.
2. Scroll down to the General section.
3. Disable Stop competing sign-in popups in the browser.
4. Try using your Google sign in once more.

I hope this helps, I have added all of you as affected users to an internal issue that has been passed on to our development team.

In addition, if you could also let us know the websites you are experiencing this trouble on that would be really useful for us to pass specific details on to the team. @cvanes if you wouldn't mind sharing the link to the app over email that would be great. Please send it to support+forum@1password.com with a link to this thread.

You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here.

I'm sorry for the disruption, let me know if there is anything else we can help with in the meantime.

ref: dev/core/core#21437