-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Developer Error on login with existing email/password after email/link enabled #1735
Comments
@lsirac before I dig into this can you confirm what the expected behavior would be if I try to sign in with Email Link for a user that was previously authenticated with Email/Password? That should work, right? |
Unfortunately this is WAI. We don't allow developers to allow both email/password and email/link. If you allow email/link, email/password will not be a supported sign-in method, and previous users using email/password won't be able to sign in. |
Thanks for clarifying @lsirac, closing as this is not a FirebaseUI issue. @hermannpoilpre if you want to voice your support for a change in the Firebase Auth behavior, file a feature request here: |
Understood, but iOS version of Firebase Auth UI works as intended : a user authenticated with password can still login with his password after enabling email/link settings. Contrary to Android version of Firebase Auth UI. So in my opinion, it is an Android Firebase Auth UI issue. |
@hermannpoilpre thanks for confirming this works differently on iOS (I don't use iOS often). I will consider this a feature request. |
I'm having the same issue, may i suggest a more explicit error message as well. It's hard to get to this ticket from "Developer error" Also, If this is by design and you can't mix and match, can you provide a recommendation on how to properly transition existing users from email/password to email/link? in other words, how to roll it out. Thank you |
It's not the same problem. Actually I use |
No workaround? Looks like I will have to revert all link change and go back to password auth for now 😓 |
Environment
Description
Our application actually uses email/password authentication.
We want to use email/link.
Email/link authentication works fine with new users.
With an already existing user who used to log with email/password, we get a "Developer Error" after validating their email.
ProviderUtils.fetchSortedProvider
compares providers link to user email (password) and providers enabled by the app (emailing, google, facebook)email/link or password are considered as a provider instead of a method of Email provider as Firebase documentation suggest https://firebase.google.com/docs/auth/android/email-link-auth#differentiating_emailpassword_from_email_link
Steps to reproduce:
Observed Results:
"Developer Error" Toast displayed
Stacktrace :
Expected Results:
Password screen must be displayed or an email must be send to login via a link
Relevant Code:
The text was updated successfully, but these errors were encountered: