-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frequent crashes #47
Comments
Those bursts of requests seem to be related the phone taking too long to respond, probably because of something else running. Would be interesting to see what effect this has when there are network interruptions. |
I noticed that the default behavior of the watch app is to immediately retry sending the message on an app_sync error. I also noticed that (for me, anyway) the chances of a successive app_sync error once one has happened are almost 100%, so it ends up sending APPSYNCANDMSG_RETRIES_MAX messages to the phone, which in turn will queue up that many XMLHttpRequests to the nightscout endpoint. Eventually, the majority of these will return, but it's like hitting the refresh button on the server 50 times as fast as you can and then sending all that data to the watch over and over again. I set mine to try a couple of times at 10 second intervals and then just wait till the next minute tick to try after that. |
Usually this is a problem if your phone is low on resources. Try closing open applications and freeing space on the phone |
Where is APPSYNCANDMSG_RETRIES_MAX set at? |
// App Sync / Message retries, for timeout / busy problems |
I don't know if it is a quirk with my setup, but I have been experiencing almost constant crashes by the watch app. Upon reviewing log entries, it appeared to be crashing after waves of 5 or more rapid attempts to resend a message to the JavaScript portion of the app. After changing APPSYNCANDMSG_RETRIES_MAX to 0, the crashes have gone away and my watch's battery life is much improved, probably because the bluetooth interface has a chance to shut down when the phone is busy and waiting on the JavaScript engine to start up.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: