Hello,
I am getting an invalid redirect_uri parameter value when redirecting users to the authorization page . The redirect_uri parameter matches the CallBack URL on my application settings (I have verified this many times!) . The following is the URL where we are redirecting:
I also have http://localhost:8080 configured for development, and the bizzarre thing is that that one works well.
Any ideas?
Thanks and regards,
Jorge
Answered! Go to the Best Answer.
It turns out that there was indeed a difference in the URL and the setting on my app. After correcting this everything is working A-OK!
It is good to verify things twice, thrice and why not, a fourth time.
I am using FitBit api to get user's data in my Android app, It doesn't communicate with any server for using in App. For implementating oAuth, I'm using Chrome custom Tabs, When I 'Allow' app to access user's fitbit data, it is givin me ERR_UNKNOWN_URL_SCHEME.
My Callback URL : <myappname>://logincallback
In manifest,
<data
android:host="logincallback"
android:scheme="myappname" />
Best Answer
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.
@nikitatech: Might need to ask in an Android developer-specific support forum, as this doesn't seem to be specific to Fitbit. Only thing I could find when searching for this error is that there was a bug in an older version of Chrome for Android: https://bugs.chromium.org/p/chromium/issues/detail?id=181186
Best AnswerI am having the same problem as you, but I've checked, double-checked, and triple-checked, and my URL is the one I found in the personal Intraday Github project (and yes, I did replace YOUR_PROJECT_KEY with my key): https://script.google.com/macros/d/YOUR_PROJECT_KEY/usercallback
This is where I got my script: https://github.com/simonbromberg/googlefitbit.
What might I be doing wrong? I have NO experience with this stuff, and have just followed the directions on Github.
Best AnswerCan you please have a look at this?
https://community.fitbit.com/t5/Web-API-Development/Invalid-redirect-uri-parameter/m-p/2131419#M7986
Best Answer
Best Answer