The app you're trying to connect did not provide valid information to Fitbit. Please report this iss

[DigiShan]

Hi all,

I keep on trying to integrate Fitbit into Funraisin - a fundraising platform but I feel like I am going in circles.

I keep getting this message everytime I press the Fitbit button to connect as a user -
"The app you're trying to connect did not provide valid information to Fitbit. Please report this issue to them.
Developer information: invalid_request - Invalid redirect_uri parameter value"

I've looked at multiple threads to try and find an answer.

I've got my 

Redirect URL as 

https:/xxxxxx.org.au/api/fitbit/callback/

I saw on a thread that adding /api/fitbit/callback/ at the end of the redirect link works? Having just the plain .org.au/ doesn't provide me with a scope page when I go to authenticate in authorize page. 

I am lost!

[Gordon-C]

Hi @DigiShan 

If the redirect_uri in your registered application settings is set to https:/xxxxxx.org.au/api/fitbit/callback/, then the redirect_uri parameter in your authorization URL needs to be the same thing and match exactly.   Please give that a try to see if it helps you get past the error.

Gordon

[DigiShan]

Hi @Gordon-C 

The Authorization URL is - https://www.fitbit.com/oauth2/authorize?response_type=code&client_id=23929Q&scope=activity+cardio_fi...

 Looking at the Authorization URL - this is the Redirect URI

"redirect_uri=https%3A%2F%2Fact.redcross.org.au%2Fapi%2Ffitbit%2Fcallback%2F" 
 
In my registered application settings it is https:/xxxxxx.org.au/api/fitbit/callback/. What are my next steps?

When I click the URL - I am not getting the same message as I was yesterday - "The app you're trying to connect did not provide valid information to Fitbit. Please report this issue to them. Developer information: invalid_request - Invalid redirect_uri parameter value".

I am now getting a 404 page. 

Are you able to assist with next steps? 

[Gordon-C]

I tested the Authorization URL you provided and it works for me.   I would say everything is configured correctly.   Try clearing your browser history and cache, then click on the URL in this post again.  Also, if you're manually encoding the redirect URL in your authorization string, try not doing that to see what happens.  Ex.  redirect_uri=https://act.redcross.org.au/api/fitbit/callback/

Lastly, make certain you're following the guidelines in our Fitbit Platform Developer and User Data Policy by only requesting the scopes in your authorization URL that are required by your application.   You can always add more later as your project requirements expand.

Gordon

[DigiShan]

Hi @Gordon-C 

Is this what you are getting? When I test the Authorization URL - The Fitbit log in screen appears, I enter my details and it processes my log in, and then i'm directed to a 404 page not found. 

[DigiShan]

@Gordon-C 

Am I meant to create a page in my website called "https://act.redcross.org.au/api/fitbit/callback/" ? So that the authorization link can link to it? 

[Gordon-C]

Ahh....yes.   The redirect_uri should be a valid endpoint that retrieves the authorization code and exchanges it for access and refresh token.  If the endpoint does not exist, the 404 error is correct.   And, if you look at the URL of the page displaying the 404, you should see the authorization code.  I'm assuming this Fitbit user has already consented to share their data with your application which is the reason the consent page isn't displayed (based on your description).