01-13-2016 23:28
01-13-2016 23:28
Hello Support,
We are encountering the error shown in the screenshot below while trying to authorize new users in our application which actually aims in connecting to Fitbit for accessing tracked data of users.
Authorization process was working fine till couple of days ago. However this error started showing up since two days. What could be the reason for this issue? Do we need to fix anything in our code to resolve this error?
Thanks & Regards,
Srinivas
Answered! Go to the Best Answer.
01-13-2016 23:38 - edited 01-13-2016 23:39
01-13-2016 23:38 - edited 01-13-2016 23:39
Hi @srinivas_h,
It's likely that you are not specifying a redirect_uri parameter when sending users to the OAuth 2.0 authorization page. While this parameter is optional under certain conditions, we recommend that you include it.
Unfortunately, we currently have a bug that is breaking applications that do not include the redirect_uri. We expect to have this fixed by the end of the week. You can fix the issue immediately by passing your redirect_uri.
I apologize for this error.
01-14-2016 11:55 - edited 01-14-2016 11:56
01-14-2016 11:55 - edited 01-14-2016 11:56
The fix is now in production and you no longer need to specify the redirect uri (as long as your app has only one redirect uri; otherwise you will need to specify as usual). Sorry for the inconvenience!
01-13-2016 23:38 - edited 01-13-2016 23:39
01-13-2016 23:38 - edited 01-13-2016 23:39
Hi @srinivas_h,
It's likely that you are not specifying a redirect_uri parameter when sending users to the OAuth 2.0 authorization page. While this parameter is optional under certain conditions, we recommend that you include it.
Unfortunately, we currently have a bug that is breaking applications that do not include the redirect_uri. We expect to have this fixed by the end of the week. You can fix the issue immediately by passing your redirect_uri.
I apologize for this error.
01-14-2016 11:55 - edited 01-14-2016 11:56
01-14-2016 11:55 - edited 01-14-2016 11:56
The fix is now in production and you no longer need to specify the redirect uri (as long as your app has only one redirect uri; otherwise you will need to specify as usual). Sorry for the inconvenience!