Acknowledged
2 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
Parents
  • 1 month ago

    Getting the same error, I can extend the list of devices / firmwares where this happens:
     Venu® 3S: 11.14
     Venu® 3: 11.14, 11.16
     Venu® 3: 11.16
     fēnix® 6X Pro / 6X Sapphire / 6X Pro Solar / tactix® Delta Sapphire / Delta Solar / Delta Solar - Ballistics Edition / quatix® 6X / 6X Solar / 6X Dual Power: 27.00
     Forerunner® 265: 20.29
     fēnix® 7X / tactix® 7 / quatix® 7X Solar / EnduroTm 2: 17.28
     Forerunner® 965: 20.29
     Forerunner® 955 / Solar: 20.29

    In my case this happens when I try to call Storage.setValue in onBackgroundData in Application.AppBase.


     

     

Comment
  • 1 month ago

    Getting the same error, I can extend the list of devices / firmwares where this happens:
     Venu® 3S: 11.14
     Venu® 3: 11.14, 11.16
     Venu® 3: 11.16
     fēnix® 6X Pro / 6X Sapphire / 6X Pro Solar / tactix® Delta Sapphire / Delta Solar / Delta Solar - Ballistics Edition / quatix® 6X / 6X Solar / 6X Dual Power: 27.00
     Forerunner® 265: 20.29
     fēnix® 7X / tactix® 7 / quatix® 7X Solar / EnduroTm 2: 17.28
     Forerunner® 965: 20.29
     Forerunner® 955 / Solar: 20.29

    In my case this happens when I try to call Storage.setValue in onBackgroundData in Application.AppBase.


     

     

Children
  • 24 days 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’)