Redirect_URI : the rules and expectancies are unclear to me..

Niels Vanwingh Source

I have an issue with the redirect_url in the OAuth2 Process with the FitBit API..

User is directed to the Authorization Page in Chrome Custom Tabs (recommended). When clicked "agree", user is not redirected back to application or I get an error message.

I find the documentation on the FitBit website very unclear..

I have already set callback_uri in many different ways, with different outcomes:

I land on the Local Page with the right Auth Code No redirect because not specified:

When added /callback, I get an "error not found" message, why??:

When using a public domain, I get an error message, why is this? Oops it it not you, it is us..

Setting in the Application Page are correct.

Settings in the Manifest are the following, adapted per redirect..

<intent-filter> <action android:name="android.intent.action.VIEW"/>
<category android:name="android.intent.category.DEFAULT"/> 
<category android:name="android.intent.category.BROWSABLE"/> 
<data android:host="" 

My Questions:

  • What are the rules and expectancies regarding redirect_url in general, and for the FitBit API in particular?
  • How can I set a working redirect_url for testing purposes on local machine?
  • How can I set a working redirect_url in production before buying a domain name?


comments powered by Disqus