Custom Chrome Tabs inconsistant in giving the callback to deep link android

[pyus13]

Hi ,

As a start of oAuth 2.0, I have developed a codebase for fitbit authentication process using custom chrome tabs, as that was the strict requirement on API documentation. I have observed some weird behavior on some of the specific devices that the call back URI which is deep linked to the application using intent is not invoking my application by chrome tabs, it just stuck on custom chrome tab after hitting the Login button and stays there indefinitely with a loading indictor .  I would like to know if you received such queries/complains from other developers out there too. If it's the case what will the recommendation in order to have consistent behavior across devices.

My CallbackURI if formed in this way :  app://com.myapp/oauth-callback

I will be glad to provide you extra details in case required .

Thanks.

[JeremiahFitbit]

This seems more like an Android platform specific issue. Have you asked Google's Android support community?

[pyus13]

Thanks for your response really appreciate.

After investigation, I feel the Login button not redirecting to the callback URL page which is deep linked into the application instead it  just stuck on the login page with Loading..,  I believe if there is a problem with chrome tabs not redirecting to the app I should at least see my call back URL loaded into custom chrome tab.

Thanks.

[JeremiahFitbit]

Is the URL the tab is stuck on https://www.fitbit.com/oauth2/authorize (the OAuth 2 authorization page) or https://www.fitbit.com/login (the Fitbit.com sign in page people are redirected to first if they are not signed into www.fitbit.com already)?

[pyus13]

So I am calling 

https://www.fitbit.com/oauth2/authorize

With prompt type as login so the page is ended on a  

https://www.fitbit.com/logout?redirect=oauth2/authorize&client_id=kjhf.......

on this page After putting the correct credentials it stuck on loading, Also sometime on authorize page after clicking the allow button.

PFA Page shared by one of the users.

login page

Thanks

[pyus13]

 Hi,

@JeremiahFitbit

Wow here I found the interesting thing, it's not the Google Chrome Custom Tabs are the culprit but because of fallback implementation it was taking Samsung's Internet application and Samsung have their own implementation of Custom tabs which is exactly mock of Google's custom chrome tabs but not as much great as Google tabs are.

So now here is something for you, fitbit button clicks is not working in custom Samsung tabs and now I have tried this in my development environment and able to see this issue.

Could you please have a look ?

Thanks

[JeremiahFitbit]

Good find! I don't have a Samsung Android device to test. Have you asked Samsung's Android developer support since this seems like it's their bug?