I made a clockface called Sentinel. Looking at the memory usage while running in the simulator it bounces around 56-61kb. This is below the 65,500kb limit, so that's good. However, is it possible that having the memory usage that close to the limit might cause some watches to fail when trying to run the clockface? Is it possible that some watches might have varying amounts of usable memory that might actually be less than the 65,500kb limit? I've done everything I can think of to make this watch face as efficient as possible, considering what it does, but despite that there are two users that I know of with Versa watches that can't get the clockface to run - it loads but doesn't appear to fetch like it should. I've tested in on two separate Ionic watches paired to two different android phones, a brand new Versa Lite, and all the simulated watch options on the simulator, and they all work. But there are some Versa watches out there that just don't work.
What are some other factors that might be causing this? Too many apps loaded on the watch? Too many text message notifications? Why would Versa Lite work fine, but Versa regular doesn't? I thought they were basically the same minus a few features.
Also is there a way to get the status of the companion launcher, and to force it closed and restarted. It's not ideal having to tell people to restart their watches all the time.
Thanks!
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.
Best Answer