help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Error 16 Critical glue error

‎04-13-2019 18:53

‎04-13-2019 18:53

Searched for this particular error # but couldn't find it.

I received an Error 16 Critical glue error as I was testing file access. I was rapidly opening and reading from various json files, MUCH faster than will happen in my app (every half-second instead of once/day) and I got this during runtime. It didn't crash, and I'm actually having trouble reproducing it.

I'm just curious what it is, and I'm wondering if there wouldn't be value in releasing the entire error list.

Thanks!!

Best Answer
0 Votes
2 REPLIES 2

‎04-15-2019 07:39

‎04-15-2019 07:39

I've encountered this error when an image is significantly larger than the width and height specified in the svg. It is scaled automatically usually, but sometimes it seems to fail with this error and then the image does not appear at all. I don't think it ever happens in the simulator, but it seems to happen frequently running on the device. I scaled all my images in Gimp or some other photo editor so that the watch won't have to do it and the errors stopped. 

Best Answer

‎04-15-2019 21:13

In response to JakeScott

‎04-15-2019 21:13

Thanks for your reply. I have been very careful to size all of my images precisely, and test for the device to read in the correct resolution.

It certainly could have been a hiccup with it loading the image, as I haven't been able to reproduce it after many hundreds of file reads (that I thought was the culprit.)

I was just hoping someone would see all these error message posts and just put out the error list for us. 😁

Best Answer
0 Votes