Complete
over 5 years ago

WERETECH-6408, WERETECH-7425, WERETECH-7514

Could not reproduce.

File not found error

On real device randomly occurs error: File Not Found Error - while trying to read from Storage

Error is already quite old. From CIQ_LOG.YML I see that it occurs roughly once a day. It is not as visible as before because Watch restart automatically Watchface.

  • Hi,I finally managed to fix it, ensuring that every time you read or write a value in the storage is correct and not null. And if it is null pass a default value. If I do not understand wrong, you have given an error for passing a null value to a property. true?

  • Former Member
    Former Member over 6 years ago

    Oh, wasn't aware that bug requires more information - as it was discussed already on the old forum (at least I believe so...)

    The issue is that watchface reading from Storage randomly fail at reading/writing - throwing exception 'File not found'.

    My watchface is reading/writing to/from storage every minute and it fails usually every 2nd day - so that gives ratio how often error exist.

    -> IF for some reason you are not able to fix the error (e.g. sometimes firmware is not able to return proper storage object) give us try-catch to handle the error - nothing serious will happen there - I'll handle error on my side...

    Last error for my (currently beta version) watchface:

    Error: File Not Found Error
    Details: 'Failed invoking <symbol>'
    Time: 2019-06-16T14:28:39Z
    Part-Number: 006-B2604-00
    Firmware-Version: '13.30'
    Language-Code: pol
    ConnectIQ-Version: 3.0.11
    Store-Id: 61770156-1c4f-491f-a357-7e18892ab775
    Store-Version: 28
    Filename: 96G62234
    Appname: Meteo Watch
    Stack:
      - pc: 0x10002af2
      - pc: 0x10000a13
      - pc: 0x10000ee9

    What leads me to (top of stack)

    Storage.setValue(6,null);

    Don't know if there is anything more can do to help remove the bug or at least give us way to avoid it...

  • Yes, it also happens to me in a watchface that I am creating, it happens once a day + -.(F5x too) It is driving me crazy. From what I read is a firmware problem, some idea of how to fix it.

  • FWIW, I have also seen this intermittent error (on an F5) and have put it down to a latency issue deep in the Garmin firmware. Something to do with it not waiting long enough to retrieve the Storage data before timing out. I haven't seen it for a while

  • Would you be willing to post the YML file info?