This usually happens when the server reloads and some code/package intercepts the Meteor reload function, preventing the client from updating (which is a valid action) but then the server reloads again and tries to push another update which is newer than the one it previously wanted to send.
I saw this error when using the arsnebula:appupdate package but not when using the following:
Thanks.
mmm. Any hints on how I could track down this down? I have a ton of packages, not sure where to start
Could it be something in mdg:reload-on-resume?