Custom tabs not starting if the chrome conditions of use are not accepted
Reported by
jejef...@gmail.com,
Mar 23 2016
|
||||
Issue descriptionSteps to reproduce the problem: 1. Clear chrome app data 2. Start a custom tab What is the expected behavior? The custom tab should start What went wrong? The custom tab doesn't start if the chrome conditions of use are not accepted. The custom tabs should at least display the chrome conditions of use screen. Here's an example of the issue : https://www.youtube.com/watch?v=sC2vUrcq124 Did this work before? No Chrome version: 49 Channel: stable OS Version: 6.0 Flash Version:
,
Mar 24 2016
,
Mar 25 2016
sbirch@ WDYT? I remember we had similar discussions before.
,
Mar 25 2016
Hi, and thanks for the report! Are you connecting to the service, using http://developer.android.com/reference/android/support/customtabs/CustomTabsServiceConnection.html ?
,
Mar 25 2016
I believe this is because there is an assumption that if you can not connect to the service custom tabs are not available. In this case if you were to send the custom tabs intent without a service connection to Chrome, you would have gotten through first run and then gotten a custom tabs. So we do support it actually. We just can't connect to the service before the user has seen ToS and since a service connection is background work, we can't pop up the ToS screen during a service connection attempt.
,
Jan 5 2017
See comment #5 |
||||
►
Sign in to add a comment |
||||
Comment 1 by jejef...@gmail.com
, Mar 23 2016