05-19-2021 07:59 - edited 05-19-2021 09:46
05-19-2021 07:59 - edited 05-19-2021 09:46
I have an app that will crash/close after some minutes while the display is off. The logs don't indicate any errors. Why is this?
Answered! Go to the Best Answer.
05-22-2021 19:14
05-22-2021 19:14
Try this:
import { me } from "appbit";
me.appTimeoutEnabled = false; // Disable timeout
Best Answer05-19-2021 12:30 - edited 05-19-2021 12:30
05-19-2021 12:30 - edited 05-19-2021 12:30
Poke()ing the display every 60 seconds seems to prevent the crash. I'm lost
Best Answer05-22-2021 19:14
05-22-2021 19:14
Try this:
import { me } from "appbit";
me.appTimeoutEnabled = false; // Disable timeout
Best Answer05-24-2021 06:17
05-24-2021 06:17
Thanks for the response. Unfortunately, this did not resolve the crashing.
Best Answer05-25-2021 05:38
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
05-25-2021 05:38
Is it definitely crashing? The apptimeout is the most likely culprit.
05-25-2021 11:24
05-25-2021 11:24
I see. I had forgotten that I was using an alias for me, so me.appTimeoutEnabled was undefined. After making the correct adjustments, I seem to have the app working now. I have left it sitting for about half an hour without problems
I had eye surgery over the weekend so my eyes are still adjusting to seeing.
Best Answer05-26-2021 02:34
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
05-26-2021 02:34
Hope your eyes recover soon!
You can alias the import to make it clearer.
import { me as appbit } from "appbit";
Best Answer