Acknowledged

App Crashes Randomly (Forerunner 645)

We are experiencing an issue where our app crashes randomly on one of our devices (Forerunner 645). It appears to not occur in the simulator and it does not happen on our other device (Forerunner 245 music). We don't think that this is a memory issue as the simulator indicates that the Forerunner 645 should have a sufficient amount of memory for our app. Any advice on the cause of the crashing and how we could avoid it would be greatly appreciated.

Here is a link to a err_log.txt (there is nothing in the CIQ_LOG) that we were getting and a branch of our repo (it is a bit outdated, but it corresponds to the err_log.txt):

https://github.com/sdgriggs/GarminDiscGolf/blob/ForConnectIQTeam/err_log.txt

https://github.com/sdgriggs/GarminDiscGolf/tree/ForConnectIQTeam

9125034
Parents
  • in reply to 9125034

    Make sure you look at ciq_log.yml as well as ciq_log.bak.  If you just see pc:, you can use the debug.xml file to get back to a line number.  The watchdog trips at different levels based on the device, so maybe what you think is resolved isn't resolved for all devices or under all conditions.  For my own beta apps, I don't look at ERA but just pull the ciq_log files right from the device - it's faster

Comment
  • in reply to 9125034

    Make sure you look at ciq_log.yml as well as ciq_log.bak.  If you just see pc:, you can use the debug.xml file to get back to a line number.  The watchdog trips at different levels based on the device, so maybe what you think is resolved isn't resolved for all devices or under all conditions.  For my own beta apps, I don't look at ERA but just pull the ciq_log files right from the device - it's faster

Children
  • in reply to 9125034

    So it's  a device crash and not a app crash (goes back to a blue triangle,  Garmin is the only one that understands err_log files,  Post them here.

  • in reply to jim_m_58

    Yes, the Watchdog Tripped Error was the most recent error across both files. That error was resolved by splitting up a rather large function and has yet to resurface (although you do bring up a good point about testing it on more devices). The issue in question is instead random crashing while using the app on the Forerunner 645 (which occurs typically, but exclusively, with menu usage). These errors are showing up in the err_log.txt and err_log.bak files in the Debug folder of the device.