getRedirectResult(auth) still returns a UserCredential with a NONnull user after signing in or signing out (no redirect operation was called)

[koroman17]

First I sign in

const provider = new GoogleAuthProvider();
signInWithRedirect(auth, provider);

then I get a UserCredential with a NONnull user (of course)

const handleGetRedirectResult = async () => {
	try {
		const result = await getRedirectResult(auth);
		console.log(result);
	} catch (error) {
		console.log(error);
	}
};
handleGetRedirectResult()

then I run the same function again

handleGetRedirectResult()

I still get a UserCredential with a NONnull user @@

then I sign out

signOut(auth)

then I run the function again

handleGetRedirectResult()

I still get a UserCredential with a NONnull user again @@
I think firebase has saved the redirect data somewhere and hasn't deleted it after first getRedirectResult(auth) that when I run handleGetRedirectResult() again, it still returns a UserCredential with a NONnull user even that I have signed out

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[jbalidiong]

Hi @koroman17, thanks for the report. I was able to reproduce the behavior now. Let me check what we can do for this issue or bring someone here that can provide more context about it. I’ll update this thread if I have any information to share.

[JGSolutions]

still getting null with 9.2.0 version

[sam-gc]

@JGSolutions, do you mean getting nonnull? The PR linked above (#5617) makes it so that it will return null on subsequent calls (as is expected)

[JGSolutions]

Yes! In version 8 was getting user and credientials objects with properties. And now they are null. If that is expected then not sure why but broke my login process