Google account selection on Fitbit Authorization page doesn't work for some users

[Hielko]

Some users get stuck on the Fitbit authorization page when they have to select the Google account they use for Fitbit. These users migrated their Fitbit account to a Google account previously. The problem occurs for several users since yesterday (September 16) or today. On our test device it works fine. The users who report this issue, experience the same problem when trying to connect other apps with their Fitbit account. Previously it worked fine for these users, also after the migration to their Google account.

When they authorize our app to access their Fitbit account, the following happens:

1. First the Fitbit Sign In page is shown. Users with a Fitbit account (not migrated) login on that page with email and password, but users with a Google account have to click on "Continue with Google", so the user clicks on "Continue with Google"
2. Then the uses sees the "Choose an account" page from Google with one or more accounts
3. When the users clicks on the account the is used for Fitbit, nothing happens, so here the user gets stuck

We see this happen with several users. Is this a bug that Fitbit/Google needs to solve, or is this a problem the user can solve?

[Hielko]

It seems that users with this problem can solve it when they refresh the Google account selection page with the refresh button. This is nice for users who contact us, but many (new) users who experience this problem, will just uninstall our app due to the bad experience. This never happened before September 16, 2023, so please look into this.

[Gordon-C]

Hi @Hielko 

Thank you for reporting this problem.   Do you have a video which demonstrates this issue?   If not, I'd like to reproduce it myself.   Would you be able to answer the following?

1. What platform are the users trying to sign into your application?

2. What browser are the people using when they are presented with the "Continue with Google" page?

3. Just to confirm, this problem only occurs after a user has already migrated their account to Google?

4. Do you know if these users are trying to migrate their account to Google at this time?

[Hielko]

Hi Gordon,

Thanks for your reply. We can reproduce the issue now on several test devices. Not only with our app, but also with MyFitnessPal (when trying to connect with the Google - Fitbit account) and FatSecret. I don't have a video because of the privacy with the account screen, but I add a few screenshots. 

1. Android platform (test devices are Pixel phones, one with Android 13, one with Android 14 latest beta)
2. Browser is Chrome
3. User already migraged to Google account in the past (this also answers your question 4)

The user first gets the Fitbit authorization screen, selectes the "Continue with Google" option, and in the following screen (the Google: choose an account screen) nothing can be done, the page seems to be frozen. But when the user selects the three dots menu of the browser page and clicks on the refresh button, then the page unfreezes, and the user can select the account.

Please let me know if you need more information. 

Hielko
appyhapps.nl

[Hielko]

Hi @Gordon-C 

Any news on this? We get more and more complaints from users about this frozen Google account selection screen.

Kind regards,

Hielko

[Hielko]

Hi @Gordon-C,

Maybe you can't reproduce the issue? Can you ask more colleagues to check this issue, we keep getting reports from users all around the world with this issue. My impression is that not everyone has this problem. 

I can reproduce the problem on a Pixel 5 phone, so if you want a phone bug report or anything else, please let me know how to send you the data you need.

Kind regards,

Hielko

[Hielko]

Hello @Gordon-C 

I'm sorry, but the problem still persists. There are users all around the world experiencing a frozen Google account selection screen, when they select "Continue with Google" in the Fitbit OAuth authorization screen.

Please let me know if you need more information or if we need to report this directly with Google. 

Kind regards,

Hielko

[Gordon-C]

Hi @Hielko 

I finally got access to an Android device and I'm going to try to reproduce the problem today.   Would you please let me know what version of Android OS you can reproduce this issue?   

Thanks!

[Gordon-C]

Hi @Hielko 

I've tried several accounts and cannot reproduce the problem.   I'm going to send you an email so I can get the bug report from you and some other information about the same device.

Gordon

[Hielko]

Hi @Gordon-C I sent you the answers on your email questions, the screen recordings and a full phone bug report, in reply to the Fitbit case email that you sent me.

[Hielko]

Hi @Gordon-C 

I notice that on our test devices it is working fine now. Has the issue been solved? 

Kind regards,

Hielko

[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 have not heard a fix is available for this problem.   I will update the forum post when I get information from engineering.

[Gordon-C · Accepted solution]

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.

[Jade_87]

I'm still having this issue and have tried the chrome update still not working please help trying to use with my new pixel watch 2.

[Hielko]

Hi @Jade_87  

I suggest that you try the reload of the authorization page, as explained in my previous post (September 19, at 23:37). Or clear all the Chrome browser cookies, maybe it helps.

[Jade_87]

Hi thanks for the reply we've tried all of these things still not working

[Hielko]

Hello @Jade_87 

Then you have another problem, I suggest you create a new ticket. 

[Jade_87]

I've just tried it again a couple more times and it's worked! Thank you
connected to watch too and get my free 6 month premium subscription

[Hielko]

That's nice to hear!