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.

StachUman
Parents
  • over 5 years ago in reply to Marco

    I had fallen back to setProperty/getProperty and it works fine for me.
    No issues with access to properties in the background on WF and the number of errors had reduced at least ten times. In fact, errors related to storage had been eliminated completely.

Comment
  • over 5 years ago in reply to Marco

    I had fallen back to setProperty/getProperty and it works fine for me.
    No issues with access to properties in the background on WF and the number of errors had reduced at least ten times. In fact, errors related to storage had been eliminated completely.

Children
  • over 5 years ago in reply to Marco


    ---
    Error: File Not Found Error
    Details: 'Failed invoking <symbol>'
    Time: 2020-02-18T21:36:28Z
    Part-Number: 006-B2859-00
    Firmware-Version: '8.00'
    Language-Code: fre
    ConnectIQ-Version: 3.1.7
    Store-Id: cf4501b9-5acb-4ed7-aef3-6573e7474871
    Store-Version: 133
    Filename: A2GB1714
    Appname: CubeWatch
    Stack:
      - pc: 0x100097a4

    after one week without any error.
    BG just went on the same time of this:
            try {
                Storage.setValue("PSWEBREQUEST",mRequestType);
            }
            catch(e) {
                System.println(e.getErrorMessage());
            }        


    (0x100097a4 lines).

    even the try / catch does not work and stop the WF  (halted !)
    ??

  • over 5 years ago in reply to IB614

    good news for you.

    I can't do without storage reading in BG since properties are not updated.

    I changed some codes too, making all my saving stuff at the return of the backgroundData, no more in events !

    (No File error for some hours. even if pretty sure there will be some.)

    finaly, It just changed / reduced  the statistics of IO conflict possibilities !

    But that not solves what i could name an IO bug.