Seeing white screen when trying to connect to fitbit with google authentication

[vipinAndroid]

Hi All,

I have been struggling with an issue lately.

I open fitbit login page in webview. Directly login through username/password works fine but when I choose continue with google.

I get to see the google login screen.

After entering the correct google username/password a white page appears in the same webview and no redirection to the app happens.

I get a redirect url which is :- https://accounts.fitbit.com/torii/redirect.html?state=AYR2ddUVqtBu0GxS&code=4%2F0AX4XfWg3OEQCIMwbI9Y....

Please suggest solution for the same.

[Gordon-C]

Hi @vipinAndroid 

The URL you're receiving doesn't look correct to me.   So, I'd like to try to reproduce the problem.   Would you please provide me with the authorization URL that you're using?   I do not need your client secret or code challenges values, so you can redact those values.   

Feel free to private message me your authorization URL, if you do not want to publish it in the forums.

Thanks!

Gordon

[vipinAndroid]

Hi,

Thanks for replying. I am choosing login through google in a webview in android. So once I enter the google id/Password after clicking continue with Google I get this error chromium: [INFO:CONSOLE(1)] "Scripts may close only the windows that were opened by them.", source: https://accounts.fitbit.com/torii/redirect-fc45e731d2dfb3596e9b32dcf112cec9.js (1) and I see a white screen and no redirection happens.

But when I login using the default username/password I am able to login successfully and this is the authorization url in both the cases.

https://www.fitbit.com/oauth2/authorize?response_type=code&client_id=xxxxxx&redirect_uri=https://dem... nutrition heartrate location nutrition profile settings sleep social weight

[Gordon-C]

Hi @vipinAndroid 

Is this the first time you have tried logging in to your application using this google account?  If not, try revoking consent to your application through the fitbit.com settings -> applications, then try again.  Also, have you tried following the same steps using the OAuth 2.0 tutorial from dev.fitbit.com/apps to see if the behavior is the same?