File Not Found Error

I received a report from a user who gets a 'File Not Found Error' when using my app. I could not reproduce it on my devices or in the sim. Has anyone an idea of what can cause this error?

Error: File Not Found Error
Details: 'Failed invoking <symbol>'
Time: 2018-12-17T13:52:13Z
Part-Number: 006-B2700-00
Firmware-Version: '5.50'
Language-Code: eng
ConnectIQ-Version: 3.0.4
Store-Id: 4d598437-2092-4d76-b058-f9e4df8d567d
Store-Version: 20
Filename: 407137A5
Appname: My QRCode
Stack:
  - pc: 0x100000fc
  - pc: 0x100015e0

Top Replies

jim_m_58 over 7 years ago +1

True, but I was pointing out what julievm was doing in onUpdate was not the best way to do it ("for other reasons...") Even when file not found is fixed, it's not the best way to do this.…

All Replies

Alan.raceQs over 7 years ago

"File Not Found Error" continues to bedevil my app in production.
I have two further observations which may assist in debugging:

1. When the error occurs, it recurs on every app start. However a watch restart clears the error.

2. when it occurs in a development deployment on a device, log fails to contain module/line number details, just a reference to the memory address in the (like when running on the SDK simulator).
a) Development version, note the filename is "QsStart"

---
Error: File Not Found Error
Details: 'Failed invoking <symbol>'
Time: 2019-02-02T22:46:48Z
Part-Number: 006-B2697-00
Firmware-Version: '12.30'
Language-Code: eng
ConnectIQ-Version: 3.0.8
Filename: QS_START
Appname: QsStart
Stack:
  - pc: 0x1000650c

b) production version, note file name is 0D7465E5:

---
Error: File Not Found Error
Details: 'Failed invoking <symbol>'
Time: 2019-02-02T23:07:41Z
Part-Number: 006-B2697-00
Firmware-Version: '12.30'
Language-Code: eng
ConnectIQ-Version: 3.0.8
Store-Id: d76bf3e2-0924-470e-b86b-62f372ecc0ae
Store-Version: 23
Filename: 0D7465E5
Appname: QsStart
Stack:
  - pc: 0x10002862

I am happy to provide any further information that you could use to get to the bottom of this.

Shent-Aurkhan (SHN) over 5 years ago in reply to Alan.raceQs

hi mates!

any news on that?

since I've moved from App.getApp().getProperties to App.Storage.getValue I have this issue also.

seems to only happen on F5x/Tactix C serie and not everytime.