auth.onAuthStateChanged is not a function

[smrubin]

Version info

Angular: 1.5.5

Firebase: 3.0.3

AngularFire: 2.0.0

Other (e.g. Node, browser, operating system) (if applicable): N/A

Test case / Steps to Reproduce / Actual Behavior

The following code:

myApp.factory("Auth", ["$firebaseAuth",
  function($firebaseAuth) { 
    var ref = firebase.database().ref();    
    var auth = $firebaseAuth(ref);     
    return auth;
  }
]);

is producing the following error:

angular.min.js:formatted:3483TypeError: auth.onAuthStateChanged is not a function
    at https://cdn.firebase.com/libs/angularfire/2.0.0/angularfire.js:1008:20
    at Object.n [as promise] (https://ajax.googleapis.com/ajax/libs/angularjs/1.5.5/angular.min.js:133:427)
    at Object.FirebaseAuth._initAuthResolver (https://cdn.firebase.com/libs/angularfire/2.0.0/angularfire.js:1001:26)
    at Object.FirebaseAuth (https://cdn.firebase.com/libs/angularfire/2.0.0/angularfire.js:802:38)
    at https://cdn.firebase.com/libs/angularfire/2.0.0/angularfire.js:790:28
    at new <anonymous> (http://localhost:4000/auth/AuthCtrl.js:5:22)

[grosem]

Simply call $firebaseAuth() as you already initialised the firebase app.

[volodymyr-mykhailyk]

Just tested. It works with $firebaseAuth() code

[jwngr]

As of AngularFire 2.0.0, the $firebaseAuth service now takes an instance of the Firebase auth service, not a Firebase database reference. So, try this instead:

var auth = firebase.auth();
var authService = $firebaseAuth(auth);

As alluded to above, if you have already initialized the Firebase SDK via firebase.initializeApp(), you can simply call $firebaseAuth() with no parameters and we will call firebase.auth() on your behalf:

// If firebase.initializeApp() already called
var authService = $firebaseAuth();

@AbeHaskins is putting together a PR which spits out a better error message for this and we should cut a 2.0.1 release sometime today with that change. He'll also update the migration guide to include this slight change in behavior. The code above should resolve your issue though.

[jwngr]

Updated error message went out with the 2.0.1 release.