Question

I am trying to somehow handle a scenario in which I am getting a corrupted application state:

1. I first open the same app in two browser windows.
2. Turn off wi-fi (or 3g) – connection becomes stale because it was not closed from the remote server.
3. Perform a write operation in the first tab (the second tab will of course not update reactively).
4. Turn on wi-fi.
5. Perform a second write in the first tab (the second tab will now update reactively)
6. So the first tab is now in a corrupted state. The first write will never sync to the server, and if the page reloads, that change will be permanently lost.

Is there a way of handling this stale connection states? Meteor.status().connected remains true throughout this scenario. Is this a Meteor issue that needs to be resolved?

Answer 1

This issue has been tagged as a confirmed bug on Meteor’s github page

https://github.com/meteor/meteor/issues/339