'File Not Found Error' suddenly massively appearing since yesterday

Since yesterday ERA is suddenly reporting 'File Not Found' errors on my Storage.setItem calls. Does anyone notice the same? I found some topics on this error but none with a real solution. Really wondering what's going on here, as users are getting IQ crashes on this suddenly. Mostly on Venu, Vivoactive4 & Vivoactive4s. Was there maybe some firmware update on there?

Top Replies

jim_m_58 over 2 years ago in reply to KC2K +2

It's a firmware issue. Garmin needs to fix the FW. There is nothing you or the Garmin CIQ team can do about it
jim_m_58 over 2 years ago +2 verified

New public beta for the venu and va4/4s for the issues in 7.10:
https://forums.garmin.com/sports-fitness/healthandwellness/f/vivoactive-4-series/305561/new-public-beta-for-vivoactive-4-4s---sw-7-20
VAW.BE over 2 years ago in reply to _psx_ +1

I saw it now and then on ERA as well, but never had users complain about it or couldn't link crashes to it. But now it's just breaking everything it seems. Not nice to see all those negative reviews while…

All Replies

0 _psx_ over 2 years ago in reply to VAW.BE

Display Settings

Hold Letter B symbol, and select Settings symbol > System > Display

..www8.garmin.com/.../GUID-24A772E9-96DD-4B65-AC8E-42853AA2C676.html

0 VAW.BE over 2 years ago in reply to _psx_

Oh yes I'm aware of that one. But the 'Timeout' options has disappeared in there somehow.

0 VAW.BE over 2 years ago in reply to VAW.BE

Super weird, I can't reproduce on my Venu (probably as I don't really use that watch, only for testing).

Anyway, did anyone already found a solution? Code-wise or something the user can do to fix it? As far as I know all found suggestions do not work. The errors keep returning to the users...

0 jim_m_58 over 2 years ago in reply to VAW.BE

Try having the user reboot the watch. Press and hold the upper button for about 20 seconds. The watch will turn itself off. Then turn it back on.

This is different from just a power cycle, and no data is lost.

0 VAW.BE over 2 years ago in reply to jim_m_58

I've already asked users to do this, but the errors somehow keep returning they say.

0 KC2K over 2 years ago in reply to VAW.BE

The app store added a note next to the latest version of my watchface that says "auto-migrated", and they changed the last update date to 8/9. I suspect they applied a patch to all watchfaces to work with the new firmware, or some such. At any rate, as of yesterday I could not even install new watchfaces on my device, it gave me an out of memory error every time I tried (even though I have plenty). As of this morning, I am able to install new watchfaces. I suspect that all watchfaces will start working properly now, but time will tell.

0 _psx_ over 2 years ago in reply to KC2K

The second bug is that system thinks there is no enough memory.

Automigrate is rather connected with new devices not the new firmware. But maybe when Garmin knows the new firmware is different it makes automigrate.

I've switched automigrate so it is a good clue, I'll build new versions of my apps.

0 jim_m_58 over 2 years ago in reply to KC2K

Auto migration is something different.

When a new device is added, if your app is already compatible with something similar, it will be "auto migrated" to the new device. You can turn this off for your app under edit details:

Auto migration isn't involved with this at all.

0 jim_m_58 over 2 years ago in reply to _psx_

The app store doesn't have source for anything in the store. It can't change anything in the app itself.

0 KC2K over 2 years ago in reply to KC2K

Sadly, time has told that the update did not fix the issue. My watch face "crashed" and all of the other user defined watch faces downloaded to my device along with it. Only thing I can do to get them working again is to restart my watch.