Watch face crashes

Former Member over 7 years ago

My watch face users report crashes. Most of them are Fenix 3 users.

I am looking for ideas on how to debug or simulate what people might be experiencing. It's a bit like walking in a dark and trying to shoot a fly.

I already guard each value returned by get property or get parameter checking for data types, nulls, checking for existence of properties or methods themselves and having a try/catch everywhere and then some. At least 20% of my code is there to account for various possible bugs reported by others on this forum...

Yet people still experience problems and I am out of ideas.

Garmin: I really wish, we could program in one of the well tooled languages, but in the absence of that, are there any plans of improving the ability to detect problems / debug / profile and diagnose?

Any ideas, suggestions...?

Thank you so much.

jim_m_58 over 7 years ago

Ok,

could you be doing somethings that's not available on CIQ 1.x devices? (the f3 is 1.x while newer watches are often 2.x) Floors, intense minutes, DND, etc.

could you be doing something that's not available on all the watches, 1.x or 2.x, like getHeartRateHistory()? The f3 doesn't have optical HR.

(for these check the programmer's guide and look for "has" :) )

when is the problem happening? When the watchface first starts, after it's run for a while, etc?

what's in the user's ciq_log.txt? There might not be much, but maybe enough. If you don't see anything, can you email a .prg with the debug symbols (not a release build in the "build for device wizard") and get the ciq_log.tx from that? You'll see more with the debug symbols.

If this is one of your early multi-device app, there are a few things to keep at the top of your toolbox, and one of them is "has" :)

Coleman.Apps over 7 years ago

Since it's not clear that there is a bug in the SDK being reported here, I'm going to move this into the regular forums.

Thanks,
-Coleman