Time series acting strange?

[heinzehavinga]

So the library seems to work great, but as soon as I try to call on time_series the authorisation seems to act up. Other calls don't seem to create this problem. I created user token using gather_keys_cli but the tokens the error returns aren't mine so i would assume these are incorrect created signatures instead of token?

print authd_client.time_series('/activities/steps/',period='7d')
File "/Users/heinzehavinga/Desktop/scraper/scraperNew/fitbit/api.py", line 363, in time_series
return self.make_request(url)
File "/Users/heinzehavinga/Desktop/scraper/scraperNew/fitbit/api.py", line 198, in make_request
response = self.client.make_request(_args, *_kwargs)
File "/Users/heinzehavinga/Desktop/scraper/scraperNew/fitbit/api.py", line 80, in make_request
raise HTTPUnauthorized(response)
fitbit.exceptions.HTTPUnauthorized: Invalid signature or token 'XXXXXXXXXXXXXX' or token 'YYYYYYYYYYYYYYY'

[brad]

Are you getting this on every time series api call, or just sometimes? I've seen this intermittently on subscription API call, and still trying to understand the cause.

[ciaranmccormick]

I'm also getting this issue for example the auth_client.sleep() returns successfully, however auth_client.time_series('/activities/steps/', period='1d') returns HTTPUnauthorized exception.

Edit:
Using 'activities/steps' instead of '/activities/steps/' results in the request to be successful.

[manobal]

@brad: I am consistently getting "HTTPUnauthorized: Invalid signature" error on subscription api. Did you figure out the cause? Thanks.

[brad]

Sorry @manobal I haven't looked into this yet, so I don't know the cause.