• Replies 3 replies
  • Subscribers 17 subscribers
  • Views 120 views
  • Users 0 members are here
Options
Related

Update related errors / ERA

beva

I don't see the errors related to get an IQ! screen after installing an update that for example reorganises resources.

Today I uploaded an update to get rid of a system timer that failed under unknown circumstances, so in the new version there is no timer.

Because I reorganized things the function that was called by the timer does no longer check for array bounds  as it won't be triggered if the array is not populated. However I suspect after updating the watch face, the by the updated version defined system timer at times fires the new function and then it hits the fan with IQ!.

After entering another app and coming back to the watch face the issue was resolved.

I am guessing that this is what was happening, as I don't see an error in ERA.

Thoughts?

  • I have some other suspicion about ERA. I am debugging with a beta datafield (this one: https://apps.garmin.com/apps/4db70717-f1c9-442a-9f18-9d81c31e2ea0 , it was once beta, and I kept using it because I reported it to Garmin after they changed it to non-beta) and it crashed today a few times. Usually when this happens I open Garmin Connect, sync and then a few minutes later I see the report in ERA Viewer. Today this did not happen.

    So things that could cause it:

    - I used SDK 8.4.0. Maybe they fixed the error that caused ERA Viewer to pop up the error message, but they haven't fixed it 100%, so now we don't get the error message, but also no errors?

    - Unusual delay in the processing of the error reports (I tried it for a while, synced multiple times, but then gave up and uploaded a newer version to test something else. Of course after having a newer version the errors from the older version wouldn't show up no matter what)

  • in reply to flocsy🤠

    It would be nice if the older versions, or at least the previous version was available in ERA as well. This way we would get insights in the problems during updates as I guess they might be assigned to the 'to long' active version and not to the newly installed version. Best would be to restart the app directly after it has been updated, but maybe Garmin doesn't see it as a a problem cause there are no incidents registered' in ERA' :D .