Android authentication opens Fitbit app instead of browser

[levynir]

Hi,

We are using web-api with code-grant flow to connect our app to fitbit. The issue is that when redirecting to fitbit.com authorization page, the fitbit app catches the url and the user is presented with just the fitbit app and not the chrome authentication window. In the best of cases the user is presented with a question whether to open Fitbit or Chrome, which is confusing and many users select Fitbit and not Chrome.

We are not using ChromeTabs.

Any ideas?

 Example of Android prompting the user to choose handler while in the midst of authentication proccess

[devomate]

We are now encountering this problem after 8 months of successful connections from our app. This breaks device connections as most Fitbit users will have the Fitbit app installed and come to the entirely reasonable conclusion that using the Fitbit app to connect their Fitbit is the way to go.

Please fix this, quickly 🙂

[tdwright]

Ouch.

This is hurting us (and our users; who are also your users!) badly.

Please fix this ASAP!

[gamsim]

Yes +1 this problem is stopping our users from connecting their Fitibit to our App.

[mishal153]

is there a timeline when an fitbit app update will fix this ? happens to me on the latest fitbit app as i try to connect other apps to fitbit 😞 

[tdwright]

@levynir Something we're investigating is dropping the "www" from our URLs.

From our brief (and ongoing) investigations, it seems as though https://fitbit.com does not deeplink into the app, whereas https://www.fitbit.com does.

Hope it helps. Still really poor form on Fitbit's part to introduce a change that breaks stuff as badly as this has.

[levynir]

Unfortunately fitbit.com redirects to www.fitbit.com which kinda beats the purpose. We will try chrome-tabs and see if it helps. 

[hiroko_a]

A similar incident occurs also in our application.We are using web-api to connect our app to fitbit. Authentication for linking with Fitbit displays "Open Fitbit application" and "Chrome to open with another application".(Android devices) If you select the former you will not be able to successfully authenticate and you will be confused users.

Please fix so that the user does not get confused.

Or, I want us to be able to authenticate without opening the Fitbit application as before.

[tdwright · Accepted solution]

Hi all,

I've heard from Jon Barlow at Fitbit that this is fixed in version 2.87 of the Fitbit Android app, which was released a couple of days ago.

From my preliminary testing, it seems to have done the job. The Oauth flow now uses the default browser without prompting.

Thanks Jon and the Fitbit Android team!

[levynir]

Thanks @tdwright for updating. We'll check as well and post again if the issue does not resolve.

[scripfit]

what if I don't have the Fitbit application in my mobile?

It ll by default get to the login page using browser. So after signing in, the login page should redirect to the permission page. Instead, it takes me to the dashboard page.

[Gordon-C]

Hi @scripfit,

Would you please provide me with your complete authorization URL?

Thanks!

Gordon

[scripfit]

Authorization uri - https://www.fitbit.com/oauth2/authorize?client_id=22DCJ5&prompt=consent&redirect_uri=https://xxx.yyy...