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.

Kyle.ConnectIQ over 10 years ago

The 5 minute time out is a device issue that will be addressed. We'll have look into the initialize() function being called twice.

Former Member over 10 years ago

Thanks Kyle. So it's Fenix 3 specific? Do you know if there is a workaround to prevent it from timing out for the time being? (if not, is there any chance the new Fenix 3 software update will fix it?).

Kyle.ConnectIQ over 10 years ago

The fix isn't available yet, and I'm not sure when the next fenix 3 release is going to be. I've got a note to track the issue and I'll try my best to note here when it'll be in the next release.

Former Member over 10 years ago

Kyle - sorry to trouble you again - just had a quick question. Regarding the 5 min device-specific app timeout on the Fenix 3 - based on what you know about it, would something like having an open FIT file and occasionally writing to it every few minutes prevent the device from timing out the app? Thanks. (Just curious if there's something I can add to my app for the time being (until the issue is fixed) so that I can release it.)

Kyle.ConnectIQ over 10 years ago

I recommend against doing this and would wait for the new device firmware to be released to address the issue, as this is an issue with the fenix 3 and not the FR920XT or the vivoactive. As Brian said in another thread, we prefer you don't work around bugs but report them so they can be fixed.

Former Member over 10 years ago

Will do Kyle. Thanks.

jim_m_58 over 10 years ago

I recommend against doing this and would wait for the new device firmware to be released to address the issue, as this is an issue with the fenix 3 and not the FR920XT or the vivoactive. As Brian said in another thread, we prefer you don't work around bugs but report them so they can be fixed.

And when will the app store prevent a CIQ app from being loaded on a device with firmware that's too old ? :)

Former Member over 10 years ago

LastBlueJay, would it be possible to get a sample of the source code you used to perform the test? Please let me know and thanks!

Former Member over 10 years ago

Hi Jason - do you mean the 5 min app exit issue or the initialize being called twice issue? A firmware update a little while ago on the Fenix 3 fixed the 5 min time out so my app stays open as long as I would like. Regarding the initialize being called twice - I haven't checked if it has been fixed but I could put together a sample app pretty easily.

Former Member 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?)