Ticket Created
over 4 years ago

CIQQA-370

strange error from era on some devices

Error Name: System Error
Occurrences: 9
First Occurrence: 2021-05-13
Last Occurrence: 2021-05-16
Devices:
    fÄ“nix® 6 Pro / 6 Sapphire / 6 Pro Solar / 6 Pro Dual Power / quatix® 6: 16.60
    Forerunner® 245 Music: 6.20
Languages: eng, spa
Backtrace:
    PSX1_Vie.onSC:415
    PSX1_Vie.onLayout:364

minSdkVersion="2.4.0", erroor onSC calling from onLayout in line

using Toybox.Application.Storage as STO;

const STO_APP_SETT                =     "AppSett";

        var t =  
        [
            1,
            loadResource(Rez.Strings.OWL)
        ];
        STO.setValue(STO_APP_SETT, t);//<--------error

I have fenix 6 pro, and 16.60 and even changed language to eng and no error.

Is possible that is connected with full of "disk" on device?

_psx_
  • over 4 years ago in reply to _psx_

    next the same errors

    Error Name: File Not Found Error
     fÄ“nix® 6S / 6S Solar / 6S Dual Power: 15.40
    STO.setValue("keyD", dict_var);//<--------------  dict_var=["k1"=true,"k2"=true]

    Error Name: File Not Found Error
    fēnix® 6S / 6S Solar / 6S Dual Power: 15.40
    STO.setValue("keyA", array_var);//<--------------array_var=[1,"en"]

  • over 4 years ago in reply to rconradharris

    1. yes, and also ALL SDK SHOULD WORKS WELL TOO.

    2. I'm losing my patience. WHY OCCASIONALLY? How to write good soft if sdk is not good? Why Garmin deprecate function and and doesn't repeair new one. storage/properties is from 2.4 it means the bug is breeding for years. I don't understand it.

    3. As you can see it's for eng too. No unicode in key and value, number, array, maybe loadResource(Rez.Strings.OWL) but  <string id="OWL">en</string>.

  • over 4 years ago

    I've also seen this bug in the wild and been sort of tracking it for the last year or so. I still don't know much about the bug, but some things I've noticed:

    1) setProperty() always works

    2) Storage.setValue() occasionally fails with this System Error message

    3) Complete speculation, but I think it may fail on devices with something other than ENG as the language. This makes me wonder if there is some kind of Unicode error happening. Perhaps a bad encoding is getting persisted into the store causing a knock-on effect of these errors?