Equivalent of getAuth()

[Bekt]

firebase v2 has the Firebase.getAuth() that synchronously retrieves the current user.

firebase v3 has no longer has that method, but comes with firebase.auth().currentUser which is not synchronous (it is null on page load). This makes it hard to perform logic on page load -- do I redirect the user to the login page, or is the user is actually logged in?

What is the equivalent of synchronous getAuth() in v3?

[bojeil-google]

Hey Bekt,
You will have to attach an observer.
firebase.auth().onAuthStateChanged(function(user) {
if (user) {
// User is signed in.
} else {
// No user is signed in. Redirect to login page.
}
});

Bassam

[Bekt]

Hey @bojeil-google, that doesn't really solve the problem because that would always result in an infinite redirect when first logged in:

'use strict';

let firstTime = true;
function start() {
    firebase.auth().onAuthStateChanged((user) => {
        if (user) {
            console.log('authorized change');
        } else if (firstTime) {
              console.log('unauthorized change');
              firstTime = false;
              let provider = new firebase.auth.GithubAuthProvider();
              provider.addScope('user');
              firebase.auth().signInWithRedirect(provider);
        }
    });
}

window.onload = start;

[bojeil-google]

You are using the same page for login and signInWithRedirect. In that case you have to call getRedirectResult first:
auth.getRedirectResult().then(function(result) {
// When this operation succeeds, currentUser should be set.
if (!auth.currentUser) {
// We are not returning from a redirect sign in and no current user signed in.
firebase.auth().signInWithRedirect(provider);
} else {
// Either the user is already signed in or has returned from a sign in redirect.
}
});

Let me know if this doesn't solve your problem.

[Bekt]

Ah, I didn't know how getRedirectResult() fit into the workflow. Thanks!

It takes about 1-2 seconds for getRedirectResult's promise to resolve, whereas onAuthStateChanged is executed almost instantly. Do you know why this happens?

[bojeil-google]

Unfortunately, that is expected at this point. In order to resolve redirect result, some processing needs to be done and some external scripts need to be pulled in. We have plans to optimize that. In the meantime, you can show a spinner while the page loads.

[Bekt]

Ah okay, thanks for the quick explanations!

I ended up doing hacky state keep trackings with onAuthStateChanged execution and getRedirectResult promise resolve.