Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with fitbit authentication #117

Open
sjakupovic opened this issue Mar 7, 2019 · 3 comments
Open

Problem with fitbit authentication #117

sjakupovic opened this issue Mar 7, 2019 · 3 comments

Comments

@sjakupovic
Copy link

After successfully configuring the Google Fit shim I’ve tried to do the same with Fitbit, but I’m having trouble with authenticating the API. After being granting permission as an user and being redirected back to my localhost console page I get this json message:

{"type":"AUTHORIZED","details":null,"accessParameters":{"id":"[my-id]","username":"user1","shimKey":"fitbit","clientId":null,"clientSecret":null,"accessToken":null,"tokenSecret":null,"stateKey":"[my-state-key]","dateCreated":"2019-03-07T10:19:13.731","serializedToken":"[my-token]","additionalParameters":{}},"requestParameters":{"redirect_url":null}}

I’m not sure if this is a good sign or not.

After that I tried to do do a request to get heart rate data or any other data, but I get an error message "org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.openmhealth.shim.ShimException: A request for Fitbit data has failed."

I think my authentication was not successful and therefore not being able to do requests to get data

Any suggestions on how to fix this or get more info on the where the problem might be?

@sjakupovic sjakupovic changed the title Probrem with fitbit authentication Problem with fitbit authentication Mar 7, 2019
@janwillemCA
Copy link

Same here

@scarini
Copy link

scarini commented Mar 27, 2019

There was a recent thread on this topic that was resolved. Have you checked it out?
#110

@tmorriso5280
Copy link

Any updates on this? I am running into the same issue and #110 didn't quite lead me to the answer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants