Acknowledged
over 1 year ago

App Quits Unexpectedly

We are developing an app for the VivoActive 5 which uses many of Connect IQ's APIs including: Sensor, Communications, and SensorHistory. The app works very well with our Android application using your Android SDK.

The issue is that for no reason our application quits at random times. It is not an application crash because there is no crash log and there is no IQ! image. The user is not quitting the application because we have the screen locked. The application does not contain any exit() calls. OnInactive() and onStop() are both called which seems to me that the application has quit gracefully.

Please see the forum post for more information. It seems as though the OS is killing the application for no reason at random times. Sometimes the OS allows our app to run for 20 minutes, sometimes 20 hours. At some point, tapping the display to wake it up takes you to the watch face instead of the app because the OS has killed the app.

https://forums.garmin.com/developer/connect-iq/f/discussion/371444/app-quits-unexpectedly---no-crash?pifragment-1298=3#pifragment-1298=1

The people on the forum want to know if there is a Connect IQ bug or if this is intended behavior where the OS kills apps without warning.

6532415
Parents
  • over 1 year ago in reply to Brandon.ConnectIQ

    Thank you. To make sure it was not one of these limits you mentioned, I powered off the watch and powered it back on. Then from the apps menu, I ran my app. It lasted for 25 hours max and then quit. I ran it from the apps menu and not the glance menu as suggested by your docs:  

    "Apps will behave differently when they are launched from the glance list versus the activity menu. If an app is launched from the glance list, a timeout will be applied to the app. If the user does not exit the app within a given time frame, the system will terminate the app and return to the home screen. If an app is launched from the activity menu, however, it will not time out, and the user must explicitly exit your application."

    One thing to note is that my app is not an activity. I am launching it from the apps menu and not the activity menu and not the glance menu.

Comment
  • over 1 year ago in reply to Brandon.ConnectIQ

    Thank you. To make sure it was not one of these limits you mentioned, I powered off the watch and powered it back on. Then from the apps menu, I ran my app. It lasted for 25 hours max and then quit. I ran it from the apps menu and not the glance menu as suggested by your docs:  

    "Apps will behave differently when they are launched from the glance list versus the activity menu. If an app is launched from the glance list, a timeout will be applied to the app. If the user does not exit the app within a given time frame, the system will terminate the app and return to the home screen. If an app is launched from the activity menu, however, it will not time out, and the user must explicitly exit your application."

    One thing to note is that my app is not an activity. I am launching it from the apps menu and not the activity menu and not the glance menu.

Children
No Data