Chrome Update Requiring Cookies to Have SameSite

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 the SameSiteattribute. 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

[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)