Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Callback uri is not working with chrome custom tabs

I'm trying authorize my android app with fitbit and everything is ok on settin callbacks etc

 

My Wep api url format

 

https://www.fitbit.com/oauth2/authorize?client_id=xxxxx&response_type=code&redirect_uri=ycwc://authorization-completed&scope=activity+nutrition+heartrate+location+nutrition+profile+settings+sleep+social+weight&state&prompt=login

 

My Handler Activity Manifest

<intent-filter>
    <action android:name="android.intent.action.VIEW" />
    <category android:name="android.intent.category.DEFAULT" />
    <category android:name="android.intent.category.BROWSABLE" />
    <data android:scheme="ycwc" />
 
</intent-filter>

It is working fine in all devices except in samsung s5 , the user can login normaly using his account but hitting the allow or deny button is not triggering an action to pass the callback to my application

 

below is the chrome intent lanucher

CustomTabsIntent.Builder builder = new CustomTabsIntent.Builder();
builder.setShowTitle(true);
CustomTabsIntent customTabsIntent = builder.build();
customTabsIntent.intent.setFlags(Intent.FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS);
customTabsIntent.intent.setFlags(Intent.FLAG_ACTIVITY_NO_HISTORY);
customTabsIntent.launchUrl(this, Uri.parse("URL"));

I can see a loading title appears on the browser title but nothing happens can anyone help in this issue

 

Best Answer
0 REPLIES 0