How To OAuth 2.0 Login Using Chrome Custom Tabs (Fitbit API)

Fitbit API doesn't support webview anymore. So, I studied chrome custom tabs and applied in my app. But after login, when I pressed this pink button(allow button), nothing happened

Solution 1:

When authorizing agains the Fitbit API, you need to provide a redirect_uri, which is where the user will be taken after logging in. You need to provide a uri that will take the user back to your application.

To achieve that, create an intent filter and add a data tag with a custom scheme, such as myapplication://logincallback to the Activity you want to handle the login.

The intent filter will look something like this:

<intent-filter . . . >
    <data android:scheme="myapplication" android:host="logincallback" />
    . . .
</intent-filter>

Now, set the redirect_uri as mypplication://logincallback to the authorization step of the flow, and when the user clicks the pink button, it should open the Activity you added the intent filter.

You will be able to retrieve the parameters inside your activity by calling getData on the Intent.

Solution 2:

<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:host="logincallback"
                android:pathPattern=".*"
                android:scheme="myapp" />
        </intent-filter>

Suppose you have redirect_uri myapp://logincallback, then add above code in your activity in Manifest xml file and it will work.