Sam

Hi folks-- for those of you who've been able to reproduce it yourselves, what are the circumstances specifically? For example, are the browsers running in private/incognito mode? Are third-party cookies...

One more thought since this issue could be caused by numerous things. There was a recent bug in the Firebase Console that caused the wrong auth domain to be presented...

@Hamaad-Siddiqui your app works consistently for me on Android / Chrome using GitHub sign in

Hi @nadavhalfon, thanks for reaching out. Please let me know if I'm understanding this problem incorrectly-- It sounds like you're attempting to perform multi-factor sign in using linking? Is that...

I see, yeah unfortunately there's no alternative. It was an explicit design decision that two existing accounts may not be linked. Think of "linking" as more like "adding a second...

Ah yeah good catch, it's always expected to pass the auth instance. I just sent out https://github.com/firebase/firebase-js-sdk/pull/6460

Hi @harshshredding, thank you very much for this pull request! API changes of this nature go through an internal process for approval. I'm sponsoring this and will get back to...

Hi @harshshredding, thanks so much for your patience. After an internal review, we've concluded that this function should **not** itself return a user object. Instead, the function should return a...

Hi @regnaio, you can avoid this issue by following recommendations 2 or 3 in this comment: https://github.com/firebase/firebase-js-sdk/issues/6443#issuecomment-1187798276 Note that that's a totally different issue, but the underlying fix for 2...

I see, thanks for expanding on this. We can reopen this as a feature request but for now it's not on our timeline.