I have a super-odd situation where my app (Meteor 220.127.116.11) will behave properly up until the first
ping/pong and then things get strange. I have a meteor method called
updateRecord which sends off a document update which I can see is correctly applied to the remote database. The UI re-renders locally with the optimistic update but then gets rolled back after the DDP
updated message comes back. The difference between when this works (for a while, after a total app restart) and when it does not is that the DDP
changed message does not get sent in the non-working case.
The same can be observed if I manually make changes to the database using the
meteor mongo CLI. On a fresh app restart I see DDP
changed messages when I update documents. Again, after the first
ping/pong sequence these manually changes no longer get propagated to the client.
Hoping someone can direct me out of this 3-day hole!