This error occurs when our users "Block third-party cookies and site data".
To replicate the error, go to:
We always advise our users to Uncheck the blocking of third-party cookies and site data; however, some users still prefer to block it.
One can still sign in to their Gmail with this blocked. Interestingly, why can't our users sign in using the Firebase-Google OAuth provided with their third party cookies & site data blocked?
We are built with Angular2 and Firebase. Is there no way that the users can still authenticate with third-party cookies and site data blocked?
Chrome on AndroidTap the three vertical dots on the top right corner in Chrome and select Settings. Find the advanced section and go to Site Settings. Inside the site settings, tap cookies and tick the “Allow 3rd party cookies” checkbox. Close and reload the browser.
OS X / macOS UsersClick Safari > Preferences and click the “Privacy” tab. Make a note about what is currently selected. Under “Cookies and website data”, click “Always Allow”.
Click the “Privacy” tab, which is in the top panel. Navigate to “Cookies and Website Data” and un-tick the option “Block all cookies”. This will allow 3rd party cookies on Safari.
The domain you're using is deeptent.com, but the domain that firebase is authenticating against and setting cookies from is your .firebaseapp.com domain. So, yes, the cookies are considered third-party. The firebase folks really should take a harder look at how they are connecting custom domains in the firebase hosting setup. Also, see here: Use Google Firebase Authentication without 3rd Party Cookies
I had the same issue with firebase and Angular.
In your environment.ts
file, look for:
firebase: { authDomain: '<domain>.firebaseapp.com',
And in chrome settings chrome://settings/content/cookies, add the following string to the cookies whitelist:
https://[*.]firebaseapp.com
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With