Fitbit connection not being maintained

  • I can connect Fitbit to my account without issue and use Keyring Importer to pull info in. The connection works for the day that I use it.

    The next day, my connection is no longer active. To reactivate it I both need to de-authorize tokens for the app, and create a new app secret and save it in the Keyring settings.

    This issue has occurred regularly over the past month of using the Fitbit connection.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Beau Lebens

    (@beaulebens)

    Per to this, Fitbit’s tokens are “short-lived”, which means they need to be refreshed regularly. The Fitbit service in Keyring attempts to automatically refresh tokens, but I guess it’s not working.

    I’m not actively using the Fitbit service right now, so I hadn’t noticed.

    The tokens seem to claim that they expire in 28800 seconds, which is 8 hours, so that would explain what you’re seeing. I’ll have to look into the refresh_token() method and see why it’s not working, unless you wanted to look at it?

    Thread Starter david wolfpaw

    (@davidjlaietta)

    This is currently a bit beyond my skill set ?? I’ve given a look into this and creating other importers (like the Pocket one that I mentioned), but my REST API knowledge is low.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Fitbit connection not being maintained’ is closed to new replies.