Fitbit disabled oauth1 support on August 1st, 2016. This updates the module to support oauth2 via two http post requests. Fitbit returns a new refresh token every time the authentication token is refreshed. This also requires the git version of the fitgem, as the version on rubygems only supports oauth1.
Fitbit disabled oauth1 support on August 1st, 2016. This updates the module to support oauth2 via two http post requests. Fitbit returns a new refresh token every time the authentication token is refreshed. This also requires the git version of the fitgem, as the version on rubygems only supports oauth1.