Replies: 1 comment 2 replies
-
Why not? I don't understand why you wouldn't want to investigate your own code as a strong preference to requesting advice from random people on the internet without providing them any information about your project. That doesn't seem like an efficient path to understanding There is some reading to do: https://firebase.google.com/docs/auth/web/account-linking |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Good Morning!
I have a question about what happens after app version update. We received a complaint from one of the users. Here's the situation. She had an account created with
auth().createUserWithEmailAndPassword
back in 2020. Now we released version update and she updated the app. Now I don't know the exact steps taken yet but she managed to sign in with Facebook credentials. Facebook account is registered with different email than one that was used to sign in in 2020. So naturally the new account was created but here's where the problem begin. Somehow those two accounts merged and has impact on each other. I don't want to dive in into the code because issue might be there but first I need to establish why this could happened (and I'm having a hard time doing that). So my question is this: assuming that user was logged in when she updated the app is it possible that after updateauth().currentUser
wasn'tnull
and was actually user data even though we didn't invoke any sign in method yet after the update?I'm still new to programming so if there are things that I need to add or clarify, please tell.
Best regards.
Beta Was this translation helpful? Give feedback.
All reactions