I respectfully disagree, because if it never left stationary mode why was the GPS turned on, on geofence exit!?
Because we have additional trigger for motion - geofence.
Well, then don't you think that there should also be another trigger to becoming stationary if a device stays within a certain area for some time that it switches over to stationary mode!? Otherwise a device might switch to motion state based on geofence alone and never switches back to stationary just like in the reported bug? Which is a matter of time before happening on a device not if it happens
Please try version 10.1.3. It should fix the problem.
Thanks for the heads up. Will try it out and report back
So far none of my test devices encountered this bug and it looks promising, and I love the elegant way you resolved this bug by inspecting the source code on github. However since I can't manually trigger the bug I can't say with 100% confidence that it certainly is fixed. Need more time to test. Will report back in a couple of days.
Thanks alot for taking this bug report seriously and swiftly (as usual from you) resolving it. Thanks alot
Side note: there is a typo in the client versions on github, on the releases you have it set to 10.2.3 while it actually is 10.1.3. Not a big deal but wanted to bring it up to your attention
Good catch with the GitHub release. It should be fixed now.
Maybe you have a better approach than what is suggested to resolve the bug. I just don't know why doesn't it always happen and what triggers it