05-05-2016 08:09
05-05-2016 08:09
Our company purchased a bunch of Fitbits for their employees and we created an app to do internal challenges. On occassion a Fitbit device goes bad for an employee and Fitbit sends them a new device.
When they receive that new device their seems to be issues retrieving their data. We seem to have to re-subscribe them so that Fitbit will send us data when they update their device.
On a similar note, we migrated to Oauth 2 & new version of the app while doing this. We dumped our old Fitbit data during this process & tried to grab new data. It appears that someone who was using a different Fitbit device then they are now, will show 0 steps for the data from their previous device when we request it through the API. Though when the user logs on to check their stats on Fitbit they still see those steps accounted for. Then the poor developer who made this nice app gets blamed (me).
Is this normal or is there something I can do to help fix this?
Answered! Go to the Best Answer.
05-05-2016 15:45
05-05-2016 15:45
People can switch devices or use multiple devices without that affecting your application authorization or subscription notification.
Maybe people are signing up as new users instead of setting up the new device on their existing Fitbit account. You can check their user ids to confirm this.
05-05-2016 15:45
05-05-2016 15:45
People can switch devices or use multiple devices without that affecting your application authorization or subscription notification.
Maybe people are signing up as new users instead of setting up the new device on their existing Fitbit account. You can check their user ids to confirm this.
05-06-2016 07:11
05-06-2016 07:11
Thank you for confirming. I'll keep a close eye on it.