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.
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 AnswerSorry to be a bug bearer but i now get this error after the updates. This is in regards to the weather code you provided on Github. I have made no alterations to the code but it is still pulling a weather code instead of condition but also this error appears when running on an actual watch , meaning no weather data displays.
error below:
[18:57:15]TypeError: Illegal invocation
Hello, I really appreciate the new SDK and I love the new WeeklyGoal for AZM to have it available.
Are there other WeeklyGoals planned to be available (soon)? eg. Weekly Goal for Steps or Floors?
I'm asking because my heath insurance gives me some payback if I regularly meet a weekly steps goal. So the new Interface would make it much easier to implement something in the Clockface if those counts would directly come from the SDK.
Another question is related to the hourly activity. Is there also planned something to have it available in the user-activity interface to have the information if I reached the hourly goal or not (for all hours of the day where I planned to be active) ?
Thanks
Sascha
Best Answer
Fitbit Product Experts Alumni are retired members of the Fitbit Product Expert Program. Learn more
Fitbit Product Experts Alumni are retired members of the Fitbit Product Expert Program. Learn more
@JonFitbit - The import fs issue seems fixed in the 4.3.1 but not the compact built code.
4.3.1 is still producing code that is too big to fit in memory whereas 4.2 produced more compact code that fitted fine.
Can this be fixed?
Author | ch, passion for improvement.
Best Answer
Fitbit Product Experts Alumni are retired members of the Fitbit Product Expert Program. Learn more
Hi @JonFitbit - will we be getting any resolutions to the compact built code problem for 4.3.1 any time soon?
Author | ch, passion for improvement.
Best AnswerHi @TKCMuzzer and @TanviK ,
Did you manage to fix this? Getting this error as well. Looks like fitbit didn't care to test the SDK on an actual device
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.
The issue relating to the Weather API and sample weather clock has been resolved. You should recompile with the latest SDK6 version (6.0.2). Studio was updated on Thu 9th Sep.
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.
@Guy_ wrote:
@JonFitbit - The import fs issue seems fixed in the 4.3.1 but not the compact built code.
4.3.1 is still producing code that is too big to fit in memory whereas 4.2 produced more compact code that fitted fine.
Can this be fixed?
Can you point me to the thread with this discussion?
Best Answer
Best Answer