App Quits Unexpectedly - No Crash

Hello.

I have an issue similar to this: https://forums.garmin.com/developer/connect-iq/f/discussion/7705/my-app-unexpectedly-ending-during-activity-for-my-vivoactive-3

I have 2 apps that I wrote. They both are designed to run indefinitely as long as the user does not quit the apps. After some time, the VivoActive 5 display goes to sleep as expected. Sometimes, I can wake up the watch by looking at it. When that does not work, I can usually wake it up by tapping once or twice. After many hours of operation, sometimes when I wake up the watch to see my apps, they are no longer running. Instead I see the watch face (the clock). At first I thought that this was a crash but there are no error logs.

Is it possible for an app to crash and not leave a log?

If not, then will the OS kill my app if it runs too long? Is there some sort of time limit?

If not, why would my app quit? I am pretty sure I am not right swiping to leave the app. I am only taping the display to wake it up.

Thank you

Top Replies

SirLanceLot over 1 year ago +1

I have had this same issue, I think it is when a user covers the watch with the palm of their hand. This turns off the screen and sends the user back to the watch face. I think it also terminates the app…

All Replies

jim_m_58 over 1 year ago in reply to 6532415

If you do, include a simple way to reproduce it.

See https://forums.garmin.com/developer/connect-iq/w/wiki/5/bug-reports-faq

FlowState over 1 year ago in reply to 6532415

6532415 said:
Should I file a bug report for CIQ?

Sure. Hopefully at the very least, Garmin will verify whether this is “expected behavior” or not.

6532415 over 1 year ago

I have an update and a few more questions.

I submitted a bug report and they are looking into it. https://forums.garmin.com/developer/connect-iq/i/bug-reports/app-quits-unexpectedly?CommentSortBy=CreatedDate&CommentSortOrder=Ascending

In the meanwhile, I have been all over the API docs and these forums trying to find a workaround. I am going to try and use a Background process in the app to detect when the main app has been removed from the foreground and to wake it back up using Background.requestApplicationWake(). I understand the concepts of Background and how to pass data back and forth.

My questions are:

1) Is there a simple function call to determine if the app is running in the foreground from the Background delegate's onTemporalEvent()?

If not then I will need to write the current time from the main app to storage using setValue() and read it from the Background delegate's onTemporalEvent() using getValue() to determine if the main app is still running. This leads me to my second question:

2) does setValue() use RAM or flash? I don't want to destroy the flash by writing to it too often.

flocsy🤠 over 1 year ago in reply to 6532415

2. flash

But if you read back in the forum you might be able to find some posts that say something like what's the difference between the old (setProperty) and the new (setValue) and if I recall correctly (and if it's true and if it's on all devices...) then maybe one difference was that it is cached in the memory and only written out to the disk when the app stops.

_psx_ over 1 year ago in reply to 6532415

probably it's by deign - "saving resources", read this

https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/venu-3-now-available-on-connect-iq-sdk-manager

maybe starting session prevent from inactivation of app