06-25-2016 18:12
06-25-2016 18:12
I enter in all the correct info on the OAuth 2.0 tutorial page(https://dev.fitbit.com/apps/oauthinteractivetutorial) and it dynamically creates the link that contains all of the query parameters needed for authorization and instructs you to click on the link. When I click on the link this is the response I get:
"Developer information: unauthorized_client - The client is not authorized to request an access token using this method."
It didn't even prompt me to log on. I think this may be because I attempted to authorize from the dev version of my mobile app and got the same response and now it is somehow cached? Could it be anything else?
06-27-2016 01:38
06-27-2016 01:38
Have you used the Authorization Code Flow?
I had this problem, by swapping from Implicit Grant Flow to Authorization Code Flow it let me in.
Best Answer06-27-2016 15:58
06-27-2016 15:58
I was hoping to use the implicit flow, I imagine that it should at least function for Fitbit to offer that option?
Best Answer06-27-2016 17:34
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
06-27-2016 17:34
AUthorization Code Grant Flow and Implicit Grant Flow are both supported. https://dev.fitbit.com/docs/oauth2/
You'll need to make sure your "OAuth 2.0 Application Type" setting on https://dev.fitbit.com/apps is set to "Client" in order to use the Implicit Grant Flow.
Best Answer06-27-2016 17:41
06-27-2016 17:41
That did it! It was previous set to server, however, now I am getting an invalid request error because my callback URI is not valid. I plan on registering a custom URL on the mobile app that points to my app(myapp://fitadventures), will this not work in the browser on my laptop for testing?
Best Answer