Vivoactive v3.20 and ConnectIq SDK 1.1.4 memory leak problem?

The FW of the vivoactive (3.20) has the 1.1.3 CIQ VM, but I've been using the 1.1.4 SDK with it since 1.1.4 came out and had no problems.

Could you get the user to create a ciq_log.txt file on the va in \garmin\apps\log and when the problem occurs, send you that file? That should give you a good idea of what caused the problem.

The FW of the vivoactive (3.20) has the 1.1.3 CIQ VM, but I've been using the 1.1.4 SDK with it since 1.1.4 came out and had no problems.

Could you get the user to create a ciq_log.txt file on the va in \garmin\apps\log and when the problem occurs, send you that file? That should give you a good idea of what caused the problem.

Hi jim_m_58,
Thanks for your reply!

The file is automatically generated upon a crash I suppose, right?

Hi jim_m_58,
Thanks for your reply!

The file is automatically generated upon a crash I suppose, right?

Right now the ciq_log.txt file has to be pre-created, or nothing will be logged. There is a file on the root of the device (err_log.txt) that will get created in the event of a hard crash of the device itself.

Right now the ciq_log.txt file has to be pre-created, or nothing will be logged. There is a file on the root of the device (err_log.txt) that will get created in the event of a hard crash of the device itself.

I have to create an empty file under Garmin\app\logs with the exact name of ciq_log.txt or ciq_log.bak?

On the root I find a file err_log.bak not err_log.txt.

By the way where did you find this hint on log files?

Thanks a lot!!

I'm not sure where the ".bak" files came from. Maybe at one time you opened the ".txt" files in an editor and it created a backup?

Another hint: in the \garmin\apps\logs directory, you can create a file called <your app name>.txt, and then within a program when you do something like a Sys.println() call, that data gets saved to the "<your app name>.txt" file. useful for debugging on a real device.

As far as where I learned this, I don't recall specifically, but these files are commonly mentioned in this forum.

Generally, 1.1.4 should work fine on vivoactive 3.20 firmware. If you are able to get an error log (especially ERR_LOG.txt, which indicates a device crash), please forward it along. We're glad to help out with error logs.

Device crashes are something we want to avoid entirely, so we definitely need to investigate those.

App crashes are often due to a coding error, but not always. We can start by helping you figure out where to look to find the source of the problem, and if you believe the app crash is due to a bug in Connect IQ, we're happy to take a closer look with you.

Dear Brandon,
Here the full icq_log.txt :

in d:\projects\smartwatch\venu\TVM\api\Ant.mb (initialize:114)
in d:\projects\smartwatch\venu\TVM\api\WatchUi.mb (handleEvent:372)
TVM ERROR:
Symbol Not Found Error
Failed invoking <symbol>

Is it useful?

Thanks a lot
Stefano

Hi Brandon,
Here I attached the ERR_LOG.TXT for the crash on another Vivoactive, hope this help.

Could you investigate so far? News?

Thanks
Stefano

Hi Stefano,

The CIQ_ERR log doesn't tell me much--that's a generic Connect IQ error message. That could indicate something like attempting to use a module that hasn't been imported.

The ERR_LOG file you supplied, however, does give me something useful. It's a stack overflow and may be related to Connect IQ, but I'm not certain. Are you able to reproduce this crash, and if so, what steps do you take to cause the crash? Also, what's the name of your app? I'm not certain which one is yours. :)

Hi Stefano,

The CIQ_ERR log doesn't tell me much--that's a generic Connect IQ error message. That could indicate something like attempting to use a module that hasn't been imported.

The ERR_LOG file you supplied, however, does give me something useful. It's a stack overflow and may be related to Connect IQ, but I'm not certain. Are you able to reproduce this crash, and if so, what steps do you take to cause the crash? Also, what's the name of your app? I'm not certain which one is yours. :)

Hi Brandon,
I am sorry but I am not able to reproduce it because I don't own an actual vivoactive watch and the simulator works fine.

What I got from my App users (WatchOut! app) is that users get a crash just before entering a text with a TextPicker.

This afternoon I updated the App on the store dropping Vivoactive compatibility. Please tell me if you need the previous .iq file

Thanks!!!