Hi Mark,
We’re writing to let you know that, starting June 18, 2024, end users of web applications that work with Firebase Authentication may not be able to authenticate through the signInWithRedirect method on Chrome versions M115+.
What do you need to know?
This change will happen due to the default enablement of the Storage Partitioning feature on Chrome M115 on July 25, 2023(exact date subject to change). Existing and new Firebase apps will be allowlisted and will continue to work until June 18, 2024.
What do you need to do?
We recommend you to migrate your application to follow the best practices for using signInWithRedirect at your earliest convenience. This mitigation guide is intended for web apps using signInWithRedirect SDK method to perform sign in.
I received the below email from Google Firebase:
Hi Mark, We’re writing to let you know that, starting June 18, 2024, end users of web applications that work with Firebase Authentication may not be able to authenticate through the signInWithRedirect method on Chrome versions M115+.
What do you need to know? This change will happen due to the default enablement of the Storage Partitioning feature on Chrome M115 on July 25, 2023(exact date subject to change). Existing and new Firebase apps will be allowlisted and will continue to work until June 18, 2024.
What do you need to do? We recommend you to migrate your application to follow the best practices for using signInWithRedirect at your earliest convenience. This mitigation guide is intended for web apps using signInWithRedirect SDK method to perform sign in.
Thanks, Micah on behalf of the Firebase team
I believe this needs to be changed: https://github.com/remjx/coindrop/blob/d3d43e2b6a5e55ce990e5a7f14ac734e0a354f26/components/Auth/FirebaseAuth.tsx#L7