Hi,
I've been receiving various reports over the last few weeks of my app hanging on the Venu2/2 plus when starting a session recording.
I've oinned this down to the session not starting which causes the app to think the new session is paused and throw up both the 'started...' and paused screens at the same time. This likely results in too many timers, or one timer getting cancelled and the screen gets stuck.
To avoid this I check the call to start() returns true and if not show a 'session start failed' message.
I got the first report of someone receiving this today ( I released it today).
So....the question is: why does the session start() sometimes return false on the Venu2/2 plus, and what can I do about it?
I know stopping and starting sessions in quick succession was an issue in the past but I don't believe this user is doing that.
Can I retry the start X times, or put a timer on the start and check the recoding status X time later to see if it has started? Could the watch be full? There doesn't appear to be documentation suggesting reasons why a sessio might not start or how to work around it
Interestingly one user using the previous version says their problem was fixed with the latest version. I'm tempted to believe this is simply the reinstall resetting something rather than anything I've fixed.
Help much appreciated as I'm getting quite a few reports of the issue.
David
