Strange behaviour of firebase transaction

Question

My firebase looks like this:

This is test code (coffee script):

Answer 1

The transaction should eventually succeed, and run on the correct state of the data, but will initially run in an "uncached" state, meaning it will run against the client's local copy of the data (likely to be null), try to commit the change to the server (which will fail), and then re-try the transaction.

This is normal, and expected. If, however, the transaction does not ever succeed, I would recommend reaching out to the support folks at support@firebase.com to continue troubleshooting the problem.