Sign in with social provider broken for users created some time ago

[simonness]

I've seen that some users that have initially created their account around 1 year ago and not logged in since are prevented from logging in.

When logging in with the relevant social provider (Facebook or Google) the redirect to firebase happens as expected but on return to the app they are not logged in. If they try logging in with email they get the error message that they already have an account linked to Facebook / Google for the email address used. So they are essentially locked out, with no way to log into their account. I have confirmed that social login is working for new and other existing users.

In the case of users created some time ago could some permissions on the social provider's side have expired that are not gracefully handled by this library?

To solve this issue I have deleted the user's Firebase auth account. When doing this the user was still unable to log in with the social provider (same redirect, not logged in issue), but they could create a new account using email.

[fredericocurti]

Same issue here! bizarre

[simonness]

Hmm, it seems like the cause could be signInWithRedirect on certain browsers / OS:

• Safari 16.1+ on macOS
• iOS 16.1+
• Firefox 109+

I got an email yesterday suggesting some best practices:

https://firebase.google.com/docs/auth/web/redirect-best-practices

It makes me wonder if this library is still being maintained? The signInFlow configuration parameter defaults to "redirect" but there's no reference to this issue in the docs.