Toggling angulareFire on/off sporadically fails about angularfire HOT 4 CLOSED

Thanks for reporting this!

We'll have to reproduce this before we can troubleshoot and try a fix. And I'm probably being dense, but I don't really don't see what to do with this little snippet. It looks like pretty stock stuff.

Any chance we could get some more data? Maybe a complete repro and a little more detail about what "sporadically fail to engage" means? Specifically, under what conditions it works and which it doesn't?

from angularfire.

Sure, here's an example on jsFiddle: http://jsfiddle.net/ItsLeeOwen/QAVv4/embedded/result/

Toggle the state of angularFire a few times, and eventually it will stop syncing with the backend. I verify this by watching the Firebase Forge in my account, where I see after 2-4 toggles angularFire will stop syncing with Firebase Forge. I suppose you can verify by opening the jsfiddle in two browsers, or by noticing missing data after a refresh.

If I remove the conditional statement in line 95 of angirefire.js, angularFire makes the re-association every time.

// line 95
if (angular.equals(val, self._parse(name)($scope))) {
return;
}

from angularfire.

a workaround is manually resetting your scope variable before re-enabling angularFire.

for example:
// before calling angularFire again unset the stuff
scope.stuff = [];
var promise = angularFire('https://my.firebaseio.com/stuff', scope, 'stuff', []);

from angularfire.

Hey @itsleeowen, we just made a bunch of changes to the code recently that takes into account local changes and tries to merge them cleanly with remote data. I believe this should fix the issue you're seeing. The jsFiddle you linked isn't accessible, could you give a try with the latest version of angularFire and reopen if you're still having trouble?

from angularfire.