Reading CIQ_LOG.txt

Former Member over 7 years ago

Hello,

Some poeple send me le CIQ_LOG.txt file after crash with my watchFace.

But I don't know how to read this.

two people send me realy similar error log

ERROR: Unexpected Type Error
DETAILS:
STORE_ID: 42fc7cff9c514bc7b230c7a4c5a8f6a3
CALLSTACK:
    @PC = 0x10002f95
    @PC = 0x100029c8
    @PC = 0x10002975
    @PC = 0x10002577
    @PC = 0x10002341
    @PC = 0x10001bb5
    @PC = 0x10004873
    @PC = 0x10004206
    @PC = 0x100040da

how to use callStack adress is there some tools on eclipse ?
the store ID isn't the same that Manifest AppID: d6d9c2a2e4834eb6b694b43d720f9e2b
How can I be sure that's my watchFace which crashe ?

The error seem to be only on fr235, is there something to know about the divice ?
memory usage on simulator max to 53k

In advance, thanks for your help.

Gilles

Top Replies

Travis.ConnectIQ over 7 years ago +1

Without looking to the source, I'm pretty sure circular dependency error doesn't have a stack because the issue is detected during app shutdown.. after the work area for the app has exited. If you run…

All Replies

jim_m_58 over 7 years ago

First thing, is the .prg from the store is a release build, and doesn't have the debug symbols That's why the call stack looks like that. One thing you can do is send the user a build with the symbols (there's a checkbox in the "build for device wizard" for a release build. Make sure it's unchecked).

With 53k, is that what you see on the bottom line in the sim, or is it what you see as peak in the "view memory" window in the sim?

a1234.garmin over 7 years ago

You should always check the app: is it yours?
https://apps.garmin.com/en-US/apps/42fc7cff-9c51-4bc7-b230-c7a4c5a8f6a3

Former Member over 7 years ago

I add a "memory view" screenshot.

Did you know if "STORE_ID" is the same that "Manifest AppID" ?
How can I be sure that the crash come from my app ?

thanks,community.garmin.com/.../1333848.png

Former Member over 7 years ago

As a1234 asked, is this the app? https://apps.garmin.com/en-US/apps/4...0-c7a4c5a8f6a3

The store ID and the manifest ID are two different ID's. The store ID can be used to identify the specific app on the store, while I don't think the manifest ID should be exposed to the user in a release build. Like Jim said, if you send the user a development build with debug symbols, the callstack will become much more readable. I believe in the mean time you could try matching some of those PC values to the corresponding values in the debug.xml.

Former Member over 7 years ago

yes that's it

Former Member over 7 years ago

Hi !

I come back with news.
From the CIQ_LOG file they send me, it seems the app crash on the following code :

if(Activity.getActivityInfo() has :altitude) {
                    value = Activity.getActivityInfo().altitude.toNumber();
}

What I think is that a memorie or whatchdog_coun issue, but it don't append on simulator and not for any ones ...
how work memory managment on fr235 ? it seems not be the same that for vivoHR for exemple.
other apps could they take some memorie or others resources when there are not on screen ?

jim_m_58 over 7 years ago

Unless you're recording an activity, altitude will be null on a devices without a baro altimeter (the 235 doesn't have a baro), so when you do toNumber() on it, that's the error. You want to null check altitude.

Former Member over 7 years ago

Thanks for the info ... I have to read again the SDK doc ... I skip some major information ^^

Former Member over 7 years ago

Hello, need some help again.

The app made a circular dependency, but no detail of callstak ...

ERROR: Circular Dependency Error
DETAILS:
STORE_ID: 42fc7cff9c514bc7b230c7a4c5a8f6a3
CALLSTACK:

There is a crash device log (with datas lost for user)

2431 (Forerunner 235) SW ver: 770
Build Type: RELEASE
Commit:9223e17e663b90f5f88d1e3a1b8b9be703cb16e6
ESN: 3942904386
04/15/18 18:00:59
RTL
errnum: 0x002
r0: 0x20007540
r1: 0x000000ee
r2: 0x00107f2f
Stack frame PC, SP: 0x0011b235, 0x20007330
Call Stack - SP at 0x20007330:
        0x000e117b
        0x00107f2f
        0x000f10df
        0x00107f2f
        0x00107c85
        0x00107f2f
        0x0011091d
        0x00011511
        0x00113aef
        0x00107c9b
        0x001138df
        0x000f45a9
        0x00071517
        0x0000ffff
        0x0000ffff
        0x00030001
        0x0004df05
        0x00042235
        0x00042ba3
        0x00007fff
        0x000ef731
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
        0x00000000
Uptime: 30733627

thanks

Former Member over 7 years ago

Hello,
I upload the prg file if someone could help me to resolve the last bugs on fr235.
It seems it could crash at any time ...

Thank you