Cannot sync with existing data API

[Wokamon]

Hi,

More and more users (mostly HR Charge users) have reported that they cannot sync with the existing data API. Is this related to the recent oAuth migration since we are still using oAuth1 or the device itself?

Thank you!

Regards,

Mars

[JeremiahFitbit]

Hi Mars,

What do you mean they "cannot sync with the existing data API"? Users generally are unaware of the API. Perhaps they mean that they are having trouble syncing their Fitbit devices with Fitbit? If so, they should contact Fitbit support.

OAuth 1.0a will be supported until April 2016.

[jmitchell38488 · Accepted solution]

Hi @Wokamon is this through an application that you've developed or manage?If so, has the authentication been upgrade to oAuth 2.0? If that's the case, then it's possible that the users haven't been properly migrated from OA1 to OA2. They'll have errors when they try to sync with the application through to FitBit because they're tokens aren't valid.

But if it isn't the case, and it's just users in general trying to do things with the FitBit iOS Application, then as @JeremiahFitbit has said, customer support is their best place to ask for help.

[Wokamon]

Hi,

Thank you for your reply. It looks like the bug is quite random. We'll be upgrading to oAuth2 for better support. 

Thank you!

Wokamon