02-16-2022 09:41
Fitbit Product Experts Alumni are retired members of the Fitbit Product Expert Program. Learn more
02-16-2022 09:41
Whilst researching the screenshot issue it was necessary to install the OS Simulator 0.9.0 to test the source of the problem.
It was then discovered that clock faces that failed to even load [with an out of memory error] on OS Simulator 0.9.2 would work fine on OS Simulator 0.9.0.
It would seem that the newer SDK versions, since SDK 4.3/ 6.0 was released around July 2021 [ Announcing SDK 6.0 for Fitbit Versa 3 and Sense ], take up a much larger portion of the available 64 MB memory, or aren't loading the same way, or there is a hidden incompatibility, such that larger builds run issue a Jerryscript out of memory error.
Although the program will load and work fine on OS Simulator 0.9.0 it already won't load on a watch with firmware 32.72.1.9
Does anyone have any suggestions how to get around the lost memory so that the older watch programs can still be supported?
Things tried - removed considerable amount of code and it still wouldn't fit on OS Simulator 0.9.2 or the watch.
Since then more code has been added and it still fits on OS Simulator 0.9.0 though.
Would really like a solution, in preference to having to orphan the Ionic, Versa and Versa lite watches.
Note: Error messages are often obscure, so it could be anything that changed with SDK 4.3 working differently and producing a memory error [already there was an issue with the FS import].
Any suggestions welcome.
Author | ch, passion for improvement.
02-22-2022 04:39
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
02-22-2022 04:39
I followed up on your other thread.