Redirect from chrome browser to android app intent filter fails if user interacts with screen
Reported by
vardaan...@gmail.com,
May 5 2017
|
||||
Issue descriptionSteps to reproduce the problem: 1. Have an activity with an intent filter that has a custom scheme (ex abc://test.abc.com/whatever) 2. open a page on chrome (user clicks a button that opens the chrome browser/chrome custom tab), on that page add a delay for 5 seconds and then redirect via JS (via window.loaction() for ex) to page 2 3. page 2 does a 302 redirect to the app's deeplink (ex abc://test.abc.com/whatever) 4. If user does not touch screen during those 5 seconds on page 1, redirect works as expected 5. If user touches screen during those 5 seconds, redirect fails with ERR_UNKNOWN_SCHEME What is the expected behavior? the redirect should always work What went wrong? if used touches screen on page 1(the one with the 5 second wait followed by JS redirect), redirect fails Did this work before? N/A Chrome version: 57.0.2987.133 Channel: stable OS Version: 7.1.1 Flash Version: this issue is not present on the older native android browser.
,
May 5 2017
,
May 8 2017
,
May 18 2017
It's a bit odd, but I think it's because of the gesture requirements. We require a user gesture for redirecting to external schemes. In the case of a redirect, the gesture is carried over from the original button click. However, if the user touches the page during the redirect, the gesture is now updated to that and the redirect probably has no gesture associated with it and therefore it fails. I am not sure we can do anything about this. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ppolise...@chromium.org
, May 5 2017Components: Mobile>Intents