Could you give us more information?

Usually a "REST URI" is used to fetch some serialized json from client to server. I am not sure what it means on Android.

Thanks for the quick response. I should have been more specific. The issues
is in an OAuth flow

To authenticate via OAuth I use a URL such as this:

https://www.fitbit.com/oauth2/authorize?redirect_uri=t2gspan://logincallback&response_type=code&client_id=227GJH&scope=profile.
..

I create a Chrome tabs session and launch to this url. The server receives
and processes this request, then issues a redirect to the "redirect uri" -
uri=t2gspan://logincallback.

I have enabled a deep link (activity) in my android application that
launches when it sees this redirect uri. The activity then completes the
authentication process.

This works fine the first time I authenticate. however, in the second and
subsequent times the app is backgrounded and nothing happens (the deep link
is not activated). If I clear the Chrome cache on the Android device it
works again (once) .

This stack overflow is the same issue (only mine didn't get fixed by adding
the warmup call - I already had thst,
http://stackoverflow.com/questions/36084681/chrome-custom-tabs-redirect-to-android-app-will-close-the-app

Facing the exact same issue on Android 6.0.1, Nexus 6
Behavior is random and also changes based on setting the redirect activity to single instance"

Do you mind testing this on Chrome Dev channel and checking if your issue persists?

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot