System Error when calling Storage.setValue

Hi, I have an app that crashes when storing value in storage when invoking following code:

Storage.setValue(valueKey, moment.value());

valueKey is non null String, moment is initialized

In ERA I see following:

Error Name: System Error
Occurrences: 5
First Occurrence: 2024-06-09
Last Occurrence: 2024-06-12
Devices:
fēnix® 7X Pro: 17.23
App Versions: 0.0.5
Languages: ces
Backtrace:
DatePicker.onAccept:154

Not sure it i may be related to firmware version 17.23. Luckily that crash is from my watch so I can do more investigations on the device but I have no idea what more I can investigate.

I have no idea how to fix it.

Thanks for any help

Tom

0 flocsy🤠 4 months ago

System Error means it's not something you can fix. You can open a bug report and hope fir the best...

0 pstoppani 4 months ago

I see this crash when the watch face is updated. This is a long standing bug in the OS. As far as I can tell, after updating the watch face, the system allows the app to run before System.Storage is ready.

0 flocsy🤠 4 months ago in reply to pstoppani

If that is the reason, then maybe moving the calls to storage to another function can help? Where do you have them now?

0 _psx_ 4 months ago

There are several critical places when there is a crash, usually on the beginning (before first onUpdate() and the end of life of app

- onStart()

- getInitialView()

- initalise()

- onStop()

- ...

I haven't find work around but I didn't try to handle storage in onUpdate due to performance.

0 thubalek 4 months ago

This is not in watchface but when numeric picker returns value. See backtrace.

Also may be worth mention that that code didn't change for years and this is only bug report. Unfortunately it is in my watch

And it happens every time. And it's not reproducible in emulator. So it may be related to latest (notoriously buggy) firmware.

0 _psx_ 4 months ago in reply to thubalek

oh...

Is it the only place you save something to storage? Check free space on the watch.

0 andyj713 4 months ago in reply to _psx_

I had the same problem a few months ago, except that my watch was rebooting. I opened a bug report 23907951K1 and Garmin contacted me and I thought we were going to get it fixed. By trial and error I found out that if you don't try to save to storage very often, it's less of a problem, so they changed the status to won't fix. Good luck.

0 _psx_ 4 months ago in reply to andyj713

Strange answer as build in activity saves a lot of data to storage every few seconds and watch face every 5 minutes and usually a few bytes.

It can be a problem with hardware or the simple system's bug. I've reported it years ago but nobody reacted. Now, more people have problem because probably more devices have unfix bug.

Sorry, it's impossible to make dev's bug using setValue (unless somebody try to save forbidden types - but then error is eliminated during dev phase). I've never seen such crash on my watch, no info from user - so maybe there is no want crash :-)

0 thubalek 4 months ago

This is more problem for me as the app developer and user as I can't eat my own dogfood. I uninstalled the app and installed it again but the problem still persists.

No other appearances in ERA except mine.

0 myaro 3 days ago

I just wanted to plus-one that I've been seeing this on Venu 3 in my logs.

I added a note to the filed bug:
forums.garmin.com/.../system-error-calling-storage-setvalue-lastest-fw