You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When transitioning networks or losing connections the app is not always attempting to reconnect to the server
To Reproduce
Steps to reproduce the behavior:
Connect to a TAK Server
Change networks (for example, go off WiFi onto Cell Data
You may see Failed as the server status, and it doesn't reconnect until you restart the app
Expected behavior
Since TAK Tracker is expected to run in the background without interaction it is imperative for it to aggressively attempt reconnects and alert the user if unable to connect
Additional context
Note that this does not happen all the time - generally the app is designed to reconnect if the connection fails, though it may take one or two cycles to recognize that failure. This bug is specifically around observed cases where the connection failed and it never attempted to reconnect.
The text was updated successfully, but these errors were encountered:
Describe the bug
When transitioning networks or losing connections the app is not always attempting to reconnect to the server
To Reproduce
Steps to reproduce the behavior:
Failed
as the server status, and it doesn't reconnect until you restart the appExpected behavior
Since TAK Tracker is expected to run in the background without interaction it is imperative for it to aggressively attempt reconnects and alert the user if unable to connect
Additional context
Note that this does not happen all the time - generally the app is designed to reconnect if the connection fails, though it may take one or two cycles to recognize that failure. This bug is specifically around observed cases where the connection failed and it never attempted to reconnect.
The text was updated successfully, but these errors were encountered: