Skip to content
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

Login with existing email/password account issue. #1180

Open
eanicolas1 opened this issue Jan 30, 2024 · 1 comment
Open

Login with existing email/password account issue. #1180

eanicolas1 opened this issue Jan 30, 2024 · 1 comment

Comments

@eanicolas1
Copy link

The following issue happens for the newest versions of iOS (13.1.0, Swift, Firebase newest version as of 2024/01/30) and Android (8.0.2, Kotlin, Firebase BOM 32.7.1 (newest version)).

If you click login with email and then enter an email that already exists as Firebase email/password account, the next view is the account creation view (where you have to enter a name and new password) and not the login screen (where you could enter your existing password). Then if you click "save" top right the message appears, that the email is already linked to an existing account.

This is a new problem since this worked some days ago. Important to add, that we tried this with several email/password accounts and none was linked to another authentication provider. We also created new accounts to check this issue and it also happens for them.

This is the code to open the Firebase Auth UI for Swift:
let authUI = FUIAuth.defaultAuthUI()
authUI.delegate = self
let providers: [FUIAuthProvider] = [ FUIOAuth.appleAuthProvider(), FUIGoogleAuth(authUI: authUI), FUIEmailAuth()]
authUI.providers = providers
authUI.shouldAutoUpgradeAnonymousUsers = false
present(authUI.authViewController(), animated: true)

Any help would be appreciated a lot.

@eanicolas1
Copy link
Author

I found the reason: It's due to "email enumeration protection". If this setting is activated in Authentication settings, the problem occurs.

  1. Is there a possibility to have this feature enabled without facing this problem?
  2. You should mention this problem somewhere. I'm sure many other users will also come across this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant