Acknowledged
5 months ago

CRASH ANY DATA FIELD!

This baffled me. This crash does not produce a LOG file. I instrumented my code to write to the console and the app-specific log. Didn't make sense. So I tried a couple more DFs like this beer counter. CRASH. Every time. I expect this happens with every data field.

Here is how to reproduce this.

  • Device: Forerunner 955 (but likely happens with (many) other watches)
  • Firmware: 12.23
  • Activity: Pool Swim (but likely any activity)
  • Crash Trigger: SAVE operations (note: Discard does NOT cause a crash, only following a SAVE)

Most people, after a SAVE, will back out to the watch face, never seeing the crash. The activity is successfully saved and uploaded to Garmin Connect. But if, instead of backing out to the watch face, you page down to get back to viewing the activity screens, you'll see the data field has in fact, crashed.

My instrumented code shows this is actually what happens: After you hit SAVE, the code runs the onTimerReset() function, then runs the compute() function exactly twice, and then stops on an IQ crash. Every time.  It does not crash IN the compute() logic. It exits compute() but crashes before it enters it the 3rd time. Affects every DF I've tried.

I'll reply with an image since I can't include it here in the OP

DaveBrillhart
  • over 2 years ago

    Interesting: I have a 945 LTE and on my watch, there is no ability to go back to the data pages after saving an activity. Whether you wait a second or press a button, you're taken to the activity summary page(s). I don't of any older watches which had that ability either (although I haven't tried them all.)

    Most people, after a SAVE, will back out to the watch face, never seeing the crash.

    So are there no activity summary pages anymore? Or do you only see them if you do nothing after selecting save?

    If it makes you feel better, certain CIQ data fields crash all the time on 945 LTE, depending on the order you add them.