ERA/Crash Log Viewer - check it out if you haven't!

This is something new in the CIQ 3.1 SDK, and is really useful!

See https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/exceptional-crash-logging

When one of your app crashes on a user device, the CIQ_LOG file is automatically uploaded to garmin, and using the debug.xml (which is automatically included when you build a .iq for the store) you can easily see the crashes users are having.  It's a summary, so you can see "this is something that happened X times, on these devices, with this firmware", with actual line numbers in a stack trace and not just the PC values!

Be forewarned, that the first time you use it, you may find things that you've never heard about - the app crashes, and there's no bad review or "contact developer" about it. That happened to me just today (I'd updated an app just a couple days back).  I had a crash in an app, and the only way I knew about it, was by looking at the crash log viewer in eclipse, and the bug was easy to find and fix based on the info provided!

  • Is there currently any global issue with this service? I am already trying for the second day and still getting this error:

    "A server error has occurred. Please try again later." ;(

  • I just saw this and tried again right away, and it's working.

  • The ERA stuff is interesting but of limited use.

    I got these errors but things work fine in the simulator.

    The second error is "there needs to be a glance view" error but the sim for the Marq Athlete doesn't enable "glance view" in "Simulation" menu, 

    Error Name: Symbol Not Found Error
    Occurrences: 2
    First Occurrence: 2019-10-24
    Last Occurrence: 2019-10-24
    Devices:
    fēnix® 6 Pro / 6 Sapphire: 2.20
    App Versions: 2.5.0
    Languages: eng
    Backtrace:
    Rez.MainLayout:70


    Error Name: Illegal Access (out Of Bounds)
    Occurrences: 2
    First Occurrence: 2019-10-24
    Last Occurrence: 2019-10-24
    Devices:
     MARQTm Athlete: 5.20
    App Versions: 2.5.0
    Languages: fre
    Backtrace:
    GRouteLoaderApp.getGlanceView:69

  • Sometime it can just be a setting or condition you've not tested with the sim.  In general, I find them really useful, but admit at times it takes some head scratching to understand how it got into the state that caused the crash.

  • Hi, 

    So I was reported a crash from a user but it has never show up on the ERA so far, 

    So I asked him to send me the log file, 

    The error is written on it, but the line pc is not written anymore. How can I do ? 

  • Hi, 

    So I was reported a crash from a user but it has never show up on the ERA so far, 

    So I asked him to send me the log file, 

    The error is written on it, but the line pc is not written anymore. How can I do ? 

  • You need to use the debug.xml file associated with the device and version of your app the user is using.

    When something is seen by way of the ERA/Crash Log viewer, this translation is done for you (the debug.xml files are in the .iq, and that's how this is done.)

  • We used to have the pc with hex number to translate, but this is missing in the log file. 

    The user has fenix 6 Sapphire fw 3.1.0

    The wf is coded with ciq 3.1.4 

    (because with this one the wf runs on every device but not with the 3.1.6)