12-22-2015 15:53
12-22-2015 15:53
It is something quite strange to me, I am implementing the authorziation code grant flow with prompt=login in the first step. As expect, Fitbit prompts me for authentication. but sometimes (not very often), Fitbit will ask me to input the email/password twice, for the first try, after refresh the web page, a green notice bar will be popped up and say "You have logged out successfully." I am pretty sure that I have typed in the email/password right, and multiple people in my company have encountered this issue. May I ask why this is happening?
Answered! Go to the Best Answer.
03-10-2016 10:19
03-10-2016 10:19
The issue has been fixed.
12-24-2015 12:09
12-24-2015 12:09
Can you please share the full URLs in the address bar when this happens?
01-12-2016 13:24
01-12-2016 13:24
Finally got one case:
After put in the password and username, it will redirect me to
01-12-2016 14:22
01-12-2016 14:22
We have experienced this as well. I have also heard from a user that they tried 20 times and never got it to login.
01-12-2016 16:17
01-12-2016 16:17
Thanks for the reports. We haven't been able to reproduce yet, but are tracking this issue.
01-19-2016 08:48
01-19-2016 08:48
Hello,
I`m experiencing this issue as well.
The scenario to reproduce this behavior for me is the following:
1. Make sure you are logged out of fitbit.com with the account used for login
2. Authenticate with OAuth 2.0 with prompt = login
3.Voila
What happens next is, user gets redirected to https://www.fitbit.com/login?...
Then provides credentials and gets redirected to https://www.fitbit.com/logout?...
Provides credentials again and then is succesfully logged in.
If user is already logged in on fitbit.com when starting login procedure, then he/she is redirected directly to https://www.fitbit.com/logout?... and the problem does not occur.
Regards
Krzysztof
02-12-2016 02:39
02-12-2016 02:39
Was this ever fixed?
02-12-2016 10:32
02-12-2016 10:32
@Jaiyo: The issue seemed to be that apps that were forcing login were not specifying a redirect_uri, as it is optional when there is only one redirect URI registered.
The fix is to specify your redirect_uri on the authorization page URL if you also want to force login.
02-12-2016 11:43
02-12-2016 11:43
Hi Jeremiah, I am pretty sure that specify the redirect_uri is not the fix, as we have specified that uri but the problem is still there.
02-17-2016 12:36
02-17-2016 12:36
02-19-2016 15:15
02-19-2016 15:15
We have been able to reproduce the issue, even when redirect_uri is specified. I do not yet have an estimate to share for when it will be fixed.
03-09-2016 23:12
03-09-2016 23:12
Just checking in to see if this is fixed. Thanks
03-10-2016 10:19
03-10-2016 10:19
The issue has been fixed.