12-21-2018 12:25
12-21-2018 12:25
I was just prompted to upgrade my simulator (to version 0.6.4), and now my projects throw an error, "Error 1 Critical glue error". I am away of the Error 0 being an invalid location for a file, etc., but this I cannot figure out. If I uninstall the simulator, and install an older version, my projects run great, but I am prompted to upgrade to the newest version without ignoring the option to upgrade.
Best Answer12-21-2018 12:29
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.
12-21-2018 12:29
Could you DM a copy of your project so we can diagnose this?
Best Answer12-21-2018 12:38
12-21-2018 12:38
DM has been sent.
Best Answer12-22-2018 10:59 - edited 12-22-2018 16:08
12-22-2018 10:59 - edited 12-22-2018 16:08
I was able to identify the issue and come up with a solution. Once starting the barometer (no frequency or batch), the watch starting taking a reading every second. By stopping the barometer after the reading (and performing whatever actions in correlation with that), and then running the start parameter at an interval, I have overcome the glue error. Not sure why this just starting showing up with the new OS 3.0, but it did.
Update: I still experience the "Error 1 Critical glue error", and have determined that I can reproduce the behavior when setting something like document.getElementById("foo").style.fontFamily = "Seville". The issue is referencing "fontFamily" where a css element is "font-family". If I change the above to document.getElementById("foo").style["font-family"] = "Seville" the glue error goes away.
Update: I take the previous statement back. glue error still occurs. This only occurs in the simulator, and not if I connect to my devices.
01-20-2019 07:11
01-20-2019 07:11
Thanks, had the same problem after the update. Your solution fixed it.
Hanspeter
Best Answer