Login via google fails in IOS

[rumeshD]

Hi, sometimes when attempting to log in using a Google account in IOS safari browser, the account selection screen appears, but after selecting an account, the app returns to a blank login page. Please find the attached error logs and screenshots for reference.

Screen 1

Screen 2 (After selecting connect via google)

Screen 3 (Redirect back to the login page and nothing happens)

These are the console errors when it is redirecting back to the login page

[DorisFitbit]

Hi @rumeshD 

Thanks for posting your question. We will take a look and get back to you as soon as we can. 

[rumeshD]

Hi @DorisFitbit , any update on this? let me know if you need more info.

[DorisFitbit]

Hi @rumeshD 

I don't have updates yet. It has been shared with the internal team to test if the issue is reproducible. 

[rumeshD]

Hi @DorisFitbit , did the internal team get back to you?

[DorisFitbit]

Hi @rumeshD 

Thank you for your patience. We have a few follow-up questions to help us investigate:

1. How are you getting to the sign-in page? (e.g., entering a URL directly or being redirected from a 3rd party application?)

2. What specific URL are you loading to reach the sign-in page?

3. Are you selecting the "Continue with Google" button before entering your email and password?

4. Is there a specific reason you are using the web login instead of the Fitbit mobile app? (This helps us understand the use case)

[rumeshD]

Hi @DorisFitbit ,

We have a workout tracking application and are integrating Fitbit so we can track users’ step data. Below are the authentication steps our application follows:

• Our frontend calls an API on our backend (Node.js) to request the Fitbit authentication URL. The backend generates this URL based on the OAuth 2.0 flow described here: https://dev.fitbit.com/build/reference/web-api/authorization/authorize/

• The backend returns the URL, and the frontend redirects the user to it.

• The Fitbit login screen appears.

• The user selects “Continue with Google” and authenticates. (This is where the intermittent issue occurs on iOS devices.)

• When authentication succeeds, Fitbit redirects to a backend endpoint. Our backend validates the auth code, updates the user’s Fitbit login status, and redirects back to our frontend.

So the answers to your questions are,

1. We generate the login URL from our backend application.
2. This is an example of a generated authorization URL: (https://www.fitbit.com/oauth2/authorize?client_id=someid&redirect_uri=https%3A%2F%2Fapi-dev.example....
3. Yes
4. We are integrating Fitbit into our application so we can track user step data.

[DorisFitbit]

@rumeshD 

Thanks for providing the details. We will investigate the issue. 

[DorisFitbit]

Hi @rumeshD 

Based on the error message 'Unable to post message to https://fitbit.google.com. Recipient has origin https://accounts.fitbit.com', we think the account is a Fitbit account. Can you try entering the email address and password into the Fitbit login screen instead of pressing the "Continue with Google" button?

If this works, then you need to convert your Fitbit account to a Google account. See Moving the Fitbit Account to a Google Account.

If it doesn't work, please contact the main customer support team to debug your account.

Hope it helps!