React-google-login: Chrome Update Requiring Cookies to Have SameSite

[rishipr]

When authenticating a user with the package, I receive the following in Chrome Dev tools. Not sure if the cookie is being set on the react-google-login side, but thought I'd flag it just in case. If so, the cookie must be set with SameSite=None and Secure.

A cookie associated with a cross-site resource at <URL> was set without theSameSiteattribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set withSameSite=NoneandSecure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at <URL> and <URL>.

[7imbrook]

As a work around until google fixes their end. You can disable SameSite by default in chrome flags.

if that markdown link doesn't work chrome://flags/#same-site-by-default-cookies

[benesva4]

Is there any solution that does not require tinkering with the browser settings? And how will this affect the site after deploy? Will it still be broken?

[bdefore]

This issue may be insightful to those affected here: https://github.com/google/google-api-javascript-client/issues/561. As far as I am aware, this issue only affects those on beta channel (or more experimental) of Chrome. The popup now displays this warning underneath the account choices.

There is a recent comment mentioning that Google have a fix expected to land in January.

[scottt732]

Chrome 80 (~Feb 4) may complicate this a bit further with behavior around secure cookies changing:
https://www.chromestatus.com/feature/5633521622188032 / https://tools.ietf.org/html/draft-west-cookie-incrementalism-00

[F1LT3R]

@anthonyjgrove - do you know if this is being set in your codebase, or outside of it? I took a quick look through the code and I could not find it anywhere. If you think it's in your code, I'm willing to take a pass at fixing this. Let me know.

[lelumees]

Feels like this is causing issues still, for me it looks like the onSuccess and onFailure callbacks are not called with the SameSite flags enabled in Chrome. Disabling the flags in Chrome makes the GoogleLogin component work as expected again - both callbacks called, isSignedIn flag working etc.

Environment
react-google-login: ^5.1.20
Chrome Version 84.0.4147.105 (Official Build) (64-bit)

[Beatzoid]

I am having this same issue. My onSuccess and onFailure events are not being called. Disabling all three flags related to SameSite did not fix it.

Environment
react-google-login: ^5.1.21
Opera Version: 70.0.3728.154 (Stable build) (64-bit)