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
Currently it works usually as I have been testing. But, I have also seen it not working at times, specially when system kills the connections. Based on my investigation so far everything seems to be placed correctly to try reconnecting when the connections are removed whether by killing the app or otherwise. My guess it has something to do with number of sensors being connected, not sure if there are any shadow restrictions from system side to limit how many peripherals can be and stay connected to the device. I planned to give a couple of more days before moving the card to backlog.
I tested with 5 sensors and did not kill the app from background or open the app to foreground for a week while using the device usually with bunch of apps from my regular use, as its my personal device. I had no issue in connection after a week with any of the sensors. Within this period I also went outside, so tags were disconnected, but then reconnected automatically when I came back. I did not investigate the background data yet, but since the connections are restored I am expecting data should be ideally collected in background as usual.
So not really sure what's up with this. It could be an issue on older devices probably, or some other unknown issue. So, I am moving this and #2142 to backlog until next time.
Description:
Investigate if we will find a way to reconnect sensor if it was disconnected
The text was updated successfully, but these errors were encountered: