[Auth] signInWithRedirect doesn’t work on Chrome 115+, Safari 16.1+, and Firefox 109+

[NhienLam]

TLDR

Implementing one of the options listed in the best practices guide will be required for redirect sign-in to work on Google Chrome M115+, Firefox 109+, and Safari 16.1+.

Issue description

Starting June 24, 2024, if you’re using the Firebase Auth signInWithRedirect method without implementing one of the options listed in the best practices guide, end users will not be able to authenticate when using browsers that block third-party cookies:

• Safari 16.1+ on macOS
• iOS 16.1+
• Firefox 109+
• Google Chrome M115+

A common behavior observed is that, after signing in with their Identity Provider account (such as Google), users are redirected back to the Firebase app without being authenticated. Using Chrome Developer Tools or similar browser tools, you will see that the signInWithIdp method is not called.

Related issues:

• Login to Firebase does not work on Safari 16.1+ #6716
• Sign in with redirect blocked on firefox due to tracking cookies #7056

What do you need to do?

Follow the best practices guide to make sure the signInWithRedirect method continues to work for all users.