Our product support is receiving reports of users not being able to successfully complete the oauth authorization page on fitbit.com.
Instead of being redirected to the redirect_uri specified by us, those users are confronted with an error message saying "Sorry, we could not fulfill your request. Please contact https://contact.fitbit.com".
Multiple users encountered this error by now. None of those users received meaningfull advice from fitbit support so I'm hoping to receive some help here for our users.
* A single user was able to resolve this issue by clearing his local browser cache; for other users this did not have any effect
* Affected users will receive the same error again when retrying to authorize our application at a later date, so this is not a temporary problem for those users
* The users are seeing the error message directly after logging in on fitbit.com; they never see the oauth consent screen
Note: While some users are affected by this problem, the number of successfull authorizations outweigh those problems by a huge margin. This is to say: I don't think this is a general configuration problem on our end.
Thanks!
Marius
Best Answer
