Issue with users granting OAuth access via 'Continue with Google' button on Fitbit sign in page

[GLE-Bearable]

Hi, some of our users have experienced that when they try to grant access to fitbit data using the 'Continue with Google' option on the fitbit login page, the login page hangs. The flow is:

1. The app redirects to the Fitbit login page

2. They select `Continue with Google`

3. They are presented with a list of google accounts

4. They tap a google account

5. The page is unresponsive (they continue to see the list of google accounts)

One of our internal team has been able to replicate this, and we have a video of the flow that we can share privately, if needed.

Other observations:

- We haven't had any issues reported when logging in using email address and password.

- We have seen successful logins via google accounts (but the accounts that don't work always don't work)

- We have only had reports of this over the last few days (although this coincides with a larger number of users using the feature over the last few days).

- Users having this issue can log in to both fitbit browser and app directly using the same Google account.

- We have an OAuth2 client application which requests read-only access to fitbit

Please can you advise how to resolve?

[Gordon-C]

Hi @GLE-Bearable 

Thank you for reporting the problem.   I will send you a direct email requesting the video and some other information.

[Gordon-C]

Thank you for reporting this problem.   We have submitted a ticket to engineering and will report back when we get more information.   In the meantime, we have heard that reloading the page will make the screen responsive.   If this doesn't work for you, please let us know.

Best,

Gordon

[Gordon-C]

I found out the problem is related to a bug in Chrome.   The bug has been fixed and was pushed out on Monday, Oct 2nd.  When you get notified to update Chrome on your Android device, please do so to resolve the problem.