BUG? - App premature exit and App initialize called twice (before and after onStart()

Former Member over 10 years ago

I noticed that my App was automatically exiting after ~5 minutes. Is this behavior intentional? I put in some logging statements to make sure it wasn't crashing (see below - from Fenix 3):

LoopTimerApp::initialize - 16:13:27
LoopTimerApp::onStart - 16:13:27
LoopTimerApp::initialize - 16:13:28
LoopTimerView::onLayout - 16:13:28
LoopTimerView::onShow - 16:13:28
LoopTimerView::onHide - 16:18:7
LoopTimerApp::onStop - 16:18:8
---------------------------
LoopTimerApp::initialize - 16:19:6
LoopTimerApp::onStart - 16:19:6
LoopTimerApp::initialize - 16:19:7
LoopTimerView::onLayout - 16:19:7
LoopTimerView::onShow - 16:19:7
LoopTimerView::onHide - 16:19:12
LoopTimerApp::onStop - 16:19:12
---------------------------
LoopTimerApp::initialize - 16:19:14
LoopTimerApp::onStart - 16:19:14
LoopTimerApp::initialize - 16:19:14
LoopTimerView::onLayout - 16:19:15
LoopTimerView::onShow - 16:19:15
LoopTimerView::onHide - 16:19:18
LoopTimerApp::onStop - 16:19:18

For the first grouping - I started the app and was using it, then approx. 5 minutes later the main watch face appeared and my app had stopped running. Logs confirm that onHide -> onStop had been called and it was not a crash but a proper exit (although not user initiated). (The second and third grouping of log statements were by me entering and exiting the app manually).

The logs also show that the AppBase initialize is being called twice - before and after onStart.

Former Member over 10 years ago

Is it possible to prevent a widget from timing out and returning to the watch screen? I'd like to be able to glance at my widget during the entirety of my activity without having to use any buttons, but my widget exits after a few minutes.

jim_m_58 over 10 years ago

Is it possible to prevent a widget from timing out and returning to the watch screen? I'd like to be able to glance at my widget during the entirety of my activity without having to use any buttons, but my widget exits after a few minutes.

Widgets are meant as "quick glance" things. I think on some devices they won't revert to the WF for a minute, but on the VA, for example, they will revert in 10 seconds, unless the widget has comm permissions, and then it hangs around longer. If you want something to "hang around" a long time, it needs to be an app and not a widget.

This thread is about an app someone developed that would terminate when it shouldn't at the same distance or time...

Former Member over 10 years ago

It is not possible to prevent Widget timeout.

...I'd like to be able to glance at my [device] during the entirety of my activity without having to use any buttons...

You should use a Watch-App for this application.

travis.vitek over 10 years ago

Am I missing something? How can you access a ConnectIQ watch face or widget while recording an activity? It seems that the only application type that satisfies this requirement is a data field.

jim_m_58 over 10 years ago

I don't know whether this fits here, but I had a similar issue where my App was terminated after 8.05 km of recording (no matter how long it lasted to arrive at >8 km).

The reason was that I called the nominal clean-up and termination code in onHide(), as the template suggested, but the system invokes a strange and unwanted display without user interaction that overlays the App's view and apparently calls (correctly) onHide().

The point is why does this system screen appear, and why doesn't this happen on the simulator? (and what can be done to prevent it?)

Ok, I ran into this with the vivoactive with my CIQ running app today. The lap screen popped up at exactly 5 miles and 10 miles. Nothing crashed and things kept going, until I ended the app at 12 miles.