No more CIQ_ERR.YML

Have I missed something in error logging?

When my app crashed on a device I used to get an error report added to the end of a file named GARMIN/APPS/LOGS/CIQ_ERR.YML. When that file reached a certain size it it would get copied CIQ_ERR.BAK and a new CIQ_ERR.YML file would be started.

These days, when the app crashes there is no CIQ_ERR.YML file, the error report is written directly to CIQ_ERR.BAK.

Is this behaviour expected?

Top Replies

jim_m_58 over 2 years ago +1 verified

The yml seems to get renamed bak when the ciq_log.yml is synced to create the era report. It's not based on size, as is the case with <myapp>.txt log files

All Replies

+1 jim_m_58 over 2 years ago

The yml seems to get renamed bak when the ciq_log.yml is synced to create the era report. It's not based on size, as is the case with <myapp>.txt log files

0 Alan.raceQs over 2 years ago in reply to jim_m_58

Hmmm interesting, since it happened when I was running a side-loaded version (alpha test) of my app. No ERA report was generated.:

---
Error: Invalid Value
Details: 'Failed invoking <symbol>'
Time: 2022-12-05T00:07:41Z
Part-Number: 006-B3906-00
Firmware-Version: '10.43'
Language-Code: eng
ConnectIQ-Version: 4.1.5
Filename: C9L34940
Appname: raceQs
Stack: 
  - pc: 0x10006ea4

0 jim_m_58 over 2 years ago in reply to Alan.raceQs

You won't get an ERA for a sideload. To translate the error report, the garmin server must have info such as the debug symbols (that are in the .iq file). The renaming is so it doesn't keep trying to sync the same yml file.

0 Alan.raceQs over 2 years ago in reply to jim_m_58

Yes, I know I won't get an ERA from a side load, and since it's not getting processed by ERA, why doesn't the xml file remain? Seems odd.

0 jim_m_58 over 2 years ago in reply to Alan.raceQs

It gets renamed so it's only synced one time

0 Alan.raceQs over 2 years ago in reply to jim_m_58

OK, thanks.