Closed bchelkowski closed 3 years ago
Fixed in v1.0.8 (#18)
Looks like when the network disconnects, the wait function inside the NRTask doesn't get notified and it waits forever. I added a timeout (10 seconds), and now is not necessary to manually restart the task.
Please confirm it is working now so I can close the issue.
Thanks! Yes, now it correctly reports events after reconnect.
There is an issue with the loss of the network connection and NRTask. After connection lost and then reconnect, the task stops working even if its state is set to "run".
For now, we can create a walkaround by setting state directly for the NRTask on connection status change:
However, it would be good to have some agent function that will do this without letting know about this task at all, and maybe which will take care of events that probably will be lost after setting the state to "stop".