🐛 [firebase_auth] userChanges() stream old data after linkWithCredential on chrome

[matheus-kirchesch-old]

Bug report

Describe the bug
userChanges is streamed when we call linkWithCredential on the user, and it works fine on android, but when on chrome it streams data before the link happens, so if you check if the user isAnonymous on a listener you will see it will still be anonymous

Steps to reproduce

1. Initialize firebase as you would
2. Listen to the userChanges stream FirebaseAuth.instance.userChanges().listen((event) { print("User updated: ${event}"); });
3. SignIn anonymously auth.FirebaseAuth.instance.signInAnonymously();
4. Link the anonymous account auth.FirebaseAuth.instance.currentUser!.linkWithCredential(EmailAuthProvider.credential(email: "dsadsa@dasdas.dasdsa", password: "dasdsadsa",),);
5. Now build for android and see it working as expected
6. Then build for chrome and see that after linking the account you will receive an update on the stream but the account they give you on the stream will still not be linked

Expected behavior

For the stream be updated after the user get linked not before

Sample project

Providing a minimal example project which demonstrates the bug in isolation from your main App greatly enhances the chance of a timely fix.
Please link to the public repository URL.

---

Additional context

Add any other context about the problem here.

---

Flutter doctor

Run flutter doctor and paste the output below:

Click To Expand

PASTE OUTPUT INSIDE HERE

---

Flutter dependencies

Run flutter pub deps -- --style=compact and paste the output below:

Click To Expand

PASTE OUTPUT INSIDE HERE

---

[darshankawar]

Thanks for the report @kirchesch. I think your case is same / similar to #3356. Can you check that and confirm ?

[matheus-kirchesch-old]

It appears to be related
But i am not having the issues they do, i receive only one update on each listener as it should, and it sinks with the right data, the only problematic one ( Of the ones i use ) is when i link an account with credentials, then it sinks in the userChanges() before actually updating the user, so:

Line 1: await auth...linkWithCredentials(...) // Right here at some point the userChanges is called and it provides old data, data before linking the account
Line 2: print(auth...currentUser) // Right here the user has been linked already and you can see its not anonymous anymore

So the problem is that the logic for handling userChanges is in the delegate bound to userChanges and not in the specific area who calls linkWithCredentials

[darshankawar]

Thanks for the update. Can you provide a minimal reproducible code sample that we can use directly to analyze this further ?

[matheus-kirchesch-old]

Ofcourse give me a minute