Reloading loses session in Chrome v80

[saimonmoore]

Hi,

After spending a long time debugging my app using useAuth I realised that this issue was happening in Chrome (and in incognito mode so it doesn't appear to be any plugins), but not FF (neither in private window mode).

So I tried the example app:

https://gatsby-useauth-example.now.sh/

It works and retains the session in Safari v13.1 (14609.1.20.111.8) but session is lost in Chrome v80.0.3987.163 (and in FF v68.5.0esr) upon reloading after logging in.

I'm on (OSX Mojave 10.14.6)

[saimonmoore]

OK this is very strange, while I was generating HAR files of testing https://gatsby-useauth-example.now.sh for the different browsers (I couldn't with Safari for some reason the export button does nothing) I noticed:

• Chrome v80 is failing consistently (both in non & incognito mode)
• Safari v13.1 works both in non & incognito mode (though there's a very noticeable rerender after reload where you can temporarily see the logged out state and then you're shown as logged in again.
• But Firefox fails consistently (both in non & private mode) for https://gatsby-useauth-example.now.sh/ :( which is weird because it works for my app.

har-files.zip

[saimonmoore]

Opened a related ticket in auth0 community: https://community.auth0.com/t/failed-silent-auth-chrome-v80/40841

[matthewlynch]

Hi @saimonmoore,

Are you using a social identity provider? If so, have you configured Auth0 to use the keys generated by the social identity provider?

I'm using google as my social identity provider and I'm using Chrome v81.0.4044.92 and do not experience the issue you've described.

[nyan-matt]

FWIW, this is happening to me as well (Chrome 83.0.4103.106) with Google social identity - in my own app, as well as on https://gatsby-useauth-example.now.sh

• Chrome logs out across hard page reloads (normal and incognito modes)
• Firefox persists login across hard page reloads (normal & private modes)

I have do have my own OAuth client ids configured in Auth0 portal, and I think I have everything configured properly.

I did notice that on Chrome, if I unblock 3rd party cookies it works as expected.

Is there any update on workaround that anyone is aware of?