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

It makes sense @nicedawg, good reasoning!

Workaround for for developers of web apps affected by this bug: the bug affects the "OneTap" method, but not the "Sign in with Google" button, so a workaround is to just add the <div class="g_id_signin" .../> tag that basically displays a button that opens the typical google login popup (https://developers.google.com/identity/gsi/web/reference/html-reference#element_with_class_g_id_signin). Callbacks or redirects defined in g_id_onload will still work the same way, so no code needs to be changed. It has more friction than the OneTap button of course, and browsers can block the popup, but at least your users will have an opportunity to login.

steph_giles please keep us up to date, thanks!

Glad it helped explain your problem, @mcanaleta!

The fact that the console was showing that the request was "blocked by client" helped point me in the right direction; often that's an indication of an adblocker, which is what I first suspected, but didn't seem to be the case. But it indicated that something in the browser was blocking it.

Realizing it could be some other Chrome extension, I started to disable a bunch of extensions at the same time, but when I saw 1Password first in my list, I thought about the recent changes that detect/assist with 3rd party logins so tried disabling only that extension - and the problem went away! (If 1Password had decided to name their fantastic product ZPassword it would've taken me much longer to reach the same conclusion. :-) )

steph_giles : Can you confirm if this is a bug that is being actively worked on? Or is there something we can do on our website to prevent our users from having this same problem logging in? (We can't change their 1Password settings for them.)

Same problem here. I confirm @steph.giles workaround works for me. Thanks for reporting the issue @nicedawg, I'm curious how were you able to debug it and find the relation with 1Password, as I also spent a lot of time trying to find the cause.

@nicedawg 🙌 Thank you so much for reporting this. This thread ended several hours of my debugging why a program I'm writing using the API was having its requests blocked. Moment I turned off 1pass my feature worked.

Same issue here, it's blocking the Google one tap to be shown.
Console error message:
[GSI_LOGGER]: Check credential status returns invalid response.
GET https://accounts.google.com/gsi/status?client_id=***********&as=**************** net::ERR_BLOCKED_BY_CLIENT

https://developers.google.com/identity/gsi/web/guides/display-google-one-tap

@cvanes, @nicedawg

Thank you! I'm sorry for any inconvenience caused.

Thanks for the workaround, steph_giles . I can also confirm it resolves the issue.

Hi steph_giles, can confirm that the workaround resolves the issue and have forwarded the link to our internal app - support ID number is 131769.

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

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
```