Web API OAuth2.0 - Authorization page loads as 'Sorry, that page is following a different trail'

[jonbee75]

Hi, I've implemented the Web API with Implicit Grant Flow and had it running fine for a couple of months. However, in the past week new users for our iOS app have come across an error page when we request authorization using OAuth2 - the error page isn't an error response, as suggested in the guidance; it looks more like Fitbit's standard 404 error page, with a message in the middle 'Sorry, that page is following a different trail'. The error page shows up after having logged in, but before an authorization page shows.

This only seems to be an issue for new users looking to authorize. Existing users can still make calls for data, and obtaining a new token by re-authorizing also isn't causing any issues. I can't really understand what's causing the error page to show rather than the authorization page. My authorization call is:

https://www.fitbit.com/oauth2/authorize?response_type=token&client_id=######&redirect_uri=examplesch...

where my client ID matches that in my registered application and my redirect uri (example above but not what I have used) is a custom URL scheme, and also defined as my callback URL in the registered application on dev site.

Thanks in advance!

[Gordon-C · Accepted solution]

Hi @jonbee75,

Try changing the redirect_uri to an absolute URL.  It should read something like redirect_uri=examplescheme://callback

[jonbee75]

So simple! Thanks so much