Chrome Custom Tab closes on X509 challenge if FLAG_ACTIVITY_NO_HISTORY is set
Reported by
alan.kin...@sap.com,
May 24 2017
|
||||
Issue descriptionApplication Version (from "Chrome Settings > About Chrome"): 58.0.3029.83 Android Build Number (from "Android Settings > About Phone/Tablet"): MMB29Q Device: Nexus 5 Steps to reproduce: 1. Create a CustomTabsIntent as usual 2. call intent.setFlags(Intent.FLAG_ACTIVITY_NO_HISTORY) 2. call launchUrl with a Uri that will result in an X509 challenge Observed behavior: When Chrome Custom Tab launches, the system keychain certificate-picker dialog is promptly shown. When the dialog shows the Chrome Custom Tab closes (the background behind the dialog is black). If the dialog is dismissed, the original application's activity is shown again. Expected behavior: Chrome Custom Tab should not close when the system certificate-picker dialog is shown. The user should be able to select a certificate and the page should continue to load. Frequency: 100% Additional comments: In our use-case (OAuth) FLAG_ACTIVITY_NO_HISTORY needs to be set, otherwise when the application's activity is launched using a custom url scheme the Chrome Custom Tab remains open in the background (and there is no programmatic way to close the Chrome Custom Tab).
,
Oct 16 2017
sbirch@ to triage
,
Oct 17 2017
To update this, we did get this functionality to work. Instead of the NO_HISTORY flag we are using 2 Activities one before the custom tab and one after (the redirect receiver). The redirect activity uses FLAG_ACTIVITY_CLEAR_TOP and FLAG_ACTIVITY_SINGLE_TOP to resume the 1st activity and clear the browser tab between them.
,
Oct 18 2017
,
Oct 20 2017
Sounds good, thanks for the update. |
||||
►
Sign in to add a comment |
||||
Comment 1 by rsgav...@chromium.org
, May 25 2017Components: UI>Browser>Mobile>CustomTabs
Owner: ltian@chromium.org
Status: Assigned (was: Unconfirmed)