Acknowledged
9 months ago

System Error calling Storage.setValue() lastest FW

This bug report evolved from https://forums.garmin.com/developer/connect-iq/f/discussion/383923/system-error-calling-storage-setvalue-lastest-fw-on-venu-3-and-fr-965

I'm getting many user reports of watchface crashes. if I look in ERA these are System Errors when doing Storage.setValue(). This is happening since the latest firmware on Venu 3, FR965, FR265. Some reported other devices as well.

Quite an annoying bug, as restarting the device sometimes works, but some users reported the error is appearing again after a while.

VAW.BE
  • 7 months ago in reply to Richard.ConnectIQ

    In an earlier version of my app, I made really bad use of the Storage.setValue(), calling it every second during a soccer game (referee app) to store variables. Users reported that the app would crash midgame and just show the IQ! logo. This could happen anywhere during the game. Some users reported it happening as late as in the second half of a 2x45 min game. I can zip the code of that version and send it to [email protected] if you like.

  • 7 months ago in reply to myaro

    This has been a particularly difficult bug to reliably reproduce and track down a root cause. We have CIQ watchface source code that has occasionally caused this crash, but it is not consistent and finding the conditions that cause it have been troublesome.

    Any additional information such as the watchface you are using or if you have more CIQ source code you could provide it could help. If you have a project that you would like to share privately you can email it to [email protected].

  • 7 months ago

    I just wanted to add some "voice of the customer" here to help the community & Garmin team know how impactful this is:

    I have many of these in my email from users, but here's a random one:

    ---

    Lately, the watchface stops appearing and instead, the Garmin Connect "IQ" icon is displayed with an orange exclamation point "!". This happens spontaneously, like a bug, and after a long time it works again.
    I would attach an image if I could on this site.
    I've been using this watchface for almost a year without a problem and it would be great if it got working again.



  • 8 months ago in reply to TitanicTurtle

    This bug is slowly becoming problematic as more and more people are affected.
    For some apps it is occurring in the thousands.

    If you want to get away from the old depricated set/getProperties() api because you used it as a cache, then Storgage.set/getValue is essential. But unfortunately it is not usable like this and it is difficult to communicate the problem to the users.

    (Could only write here as a reply to a comment in case someone has the same problem - ‘An error occurred’)