getRedirectResult always returns null even though user has authenticated successfully with signInWithRedirect

[hoppybunny]

Operating System

macOS

Environment (if applicable)

React Native

Firebase SDK Version

11.0.2

Firebase SDK Product(s)

Auth

Project Tooling

React Native with Expo, currently running on the web

Detailed Problem Description

My app is built using React Native Expo framework, currently running on the web. I am implementing Google sign-in using Firebase Authentication with signInWithRedirect(). After a successful sign-in, getRedirectResult() keeps returning null instead of the expected result, even though the user is authenticated and signed in successfully.

I followed the best practices here: https://firebase.google.com/docs/auth/web/redirect-best-practices

I am currently using Option 1 as I am hosting the app on firebase, and having a custom domain.
This is what I have already done:

• I m using a custom domain and I've set the firebase config authDomain to my custom domain
• I've added the custom domain in the Authorized redirect URIs in GCP console
• I've also added my custom domain as a authorized domain in firebase console
• I've also allowed for all third party cookies.

Why is this still happening? I tried various suggestions on Stack Overflow and GitHub issues but none worked. I suspect that because signInWithRedirect forces a full page reload, the result returns as null.

Please help! Thank you

Steps and code to reproduce issue

2 ways of writing the code that I tried:

Method 1

  const handleGoogleSignIn = async () => {
    const provider = new GoogleAuthProvider();
    try {
      await signInWithRedirect(auth, provider)
      } catch (error) {
      console.error(error);
      }
  }

  // This function handles the result after the user is redirected back
const handleRedirectSignIn = async () => {
  try {
    const result = await getRedirectResult(auth); 
    alert(result) //this returns null
    if (result && result.user) {
      alert(`Welcome!`);
      router.push('/HomeScreen'); 
    } else {
      alert('User not authenticated.');
    }
  } catch (error) {
    console.error("Error during redirect sign-in:", error);
    alert('Failed to sign in with Google.');
  }
};

useEffect(() => {
  handleRedirectSignIn();  
}, []); 

Method 2:

    const provider = new GoogleAuthProvider();
    try {
      await signInWithRedirect(auth, provider)
      const result = await getRedirectResult(auth);
      if (result) {
        alert('Sign-in successful!');
        router.push('/HomeScreen');
      } else {
        alert('Failed to sign in with Google.');
      } 

[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.

[myleshk]

React Native but on the web? Sounds like a very rare combination...good luck.
BTW have you tried to pinpoint the cause by creating a minimal HTML + Webpack page to make sure if it's really React Native or other parts causing the problem?

[jbalidiong]

Hi @hoppybunny, thanks for reaching out to us and apologies for the late response. I tried replicating the issue and I wasn't able to experience the same behavior. I tried authenticating on browser on my computer and mobile and the authentication was successful and I was able to see the user object using the getRedirectResult(). I've created a repo that also uses your code snippet. Could you try running this to see if you'd encounter the same issue, let me know in case I may be missing anything.

[google-oss-bot]

Hey @hoppybunny. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[qw789]

the same problem.

[kasiakor]

the same problem, response is null from redirect

[google-oss-bot]

Hey @hoppybunny. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@hoppybunny if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.

[vedant-shah]

facing the same issue