02-28-2019 13:26
Gold Fitbit Product Experts share support knowledge on the forums and advocate for the betterment of Fitbit products and services. Learn more
02-28-2019 13:26
I've thrown together the start of a FAQ on SDK development: see here. Please let me know of any additions/corrections required. Bonus points if you can tell me me the answers, and not just the questions. 😉
I hope this is (or becomes) helpful to the SDK developer community.
Best Answer03-05-2019 12:48
03-05-2019 12:48
Hey, I've got no questions and one answer 🙂 or a note to an answer.
Regarding reliability of the Messaging API. We've just published version 1.1.0 of fitbit-asap library, which, apart from simplifying the messaging itself also features a reliability layer which resends the messages until an acknowledgment is returned from the peer, all under the hood. Check it out!
03-06-2019 00:30
Gold Fitbit Product Experts share support knowledge on the forums and advocate for the betterment of Fitbit products and services. Learn more
03-06-2019 00:30
Thanks; I'll add a reference to that.
Wanna make one for file transfer?
Please? ![]()
Best Answer03-06-2019 04:57
03-06-2019 04:57
I was under the impression that File Transfer API sends the content reliably.
Or do you mean just to simplify the API?
Best Answer03-06-2019 12:27
Gold Fitbit Product Experts share support knowledge on the forums and advocate for the betterment of Fitbit products and services. Learn more
03-06-2019 12:27
File Transfer is better, but still clogs up sometimes (even with just a couple of files in the queue). I've got extensive logs showing files that get enqueued but never get received. I believe your fitbit-asap collaborator has also experienced this.
Best Answer05-08-2019 10:11
05-08-2019 10:11
I suggest putting the logs and code which exhibits the file transfer behavior up somewhere like github and putting a link to the repo here.
Best Answer