Acknowledged
7 days ago
CIQQA-3245

ERA tool does not provide crash reports consistently

Over the past few weeks I've noticed that I'm not getting reports for all crashes.  Customers report a crash via email but the crash reports available via ERA clearly don't contain reports for these crashes (the watch is not listed or crashes shown have an obvious explanation and do not match the customers email report).

As a test I installed an beta version of an app that causes a crash.  It was installed on multiple devices, they all crashed, but I got no crash reports via ERA.

This is also been discussed here: https://forums.garmin.com/developer/connect-iq/f/discussion/396341/does-era-system-work-for-you/1935907#1935907

pstoppani
  • 7 days ago

    I have a customer that says my watch face HeXcellent crashes about every two hours!  Yet, there last crash in ERA on her watch a 7S, was on May 12.  I was able to get the crash log and it does not have a stack trace, which may be why ERA does not provide it??  If that is the reason, that is a bug because the crash report at least tells me the crash is happening and why.

    Another odd thing is that I have the app running on my watch with exactly the same settings as the customer and it works fine.  And, it is not a memory hog so there should be no way it ran out of memory.

    ---
    Error: Out Of Memory Error
    Details: 'Failed invoking <symbol>'
    Time: 2025-05-20T20:55:06Z
    Part-Number: 006-B4374-00
    Firmware-Version: '20.22'
    Language-Code: eng
    ConnectIQ-Version: 5.0.2
    Store-Id: 596643c4-c0a1-44a3-8404-fc26ac306541
    Store-Version: 28
    Filename: F59F1945
    Appname: HeXcellent
    Stack:

  • 7 days ago

    Interesting!. It looks like they did some fix recently. I looked at ERA Viewer now, and I see some "new" reports since 2025-05-10, that were not there before. This includes errors of a beta app that for sure I can say that after the crash I synced both Garmin Connect and Connect IQ several times, and checked in ERA for several days, and the error wasn't there, and now (2025-05-21) I certainly see the error from 11 days ago.

    I also saw other errors from real users since 10th May that I haven't seen previously (though in theory some of those could be explained by the user only syncing after a week.)