So, this question was surprisingly similar to my own which I just figured out with help from the folks over at the Angular IRC channel… are you, by chance, setting up your controller though ng-controller
? I had:
<div ng-controller="myCtrl">
… when it should have been removed:
<div>
… because I was setting up the controller in the resolve on the router. That’s what I was doing and it was causing this very issue. You can see more here: