Google Chrome failed to launch url from shortcut
Reported by
michael...@gmail.com,
May 29 2018
|
|||||||||
Issue description
Chrome Version : 62.0.3202.84
URLs (if applicable) : any url
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari:
Firefox: OK
Edge: FAIL
Samsung Internet: OK
What steps will reproduce the problem?
(1)Provision an Android device as a single-purpose device, and enter lock task mode with the default launcher
(2)Create a shortcut on desktop with ACTION_VIEW and url in it
(3)Set Chrome as default browser and click on the shortcut
What is the expected result?
Chrome launched and load the url.
What happens instead?
Chrome launched but didn't load the url
Please provide any additional information below. Attach a screenshot if
possible.
During the launch process, Chrome checked KeyguardManager.inKeyguardRestrictedInputMode and the method returned true, which caused Chrome bypassed loading the url.
It doesn't always reproduce, but restart the device several time can make it happen.
,
May 30 2018
,
May 30 2018
michaelyzm@ -- Thanks for reporting this issue. In order for the better understanding of the issue could you please provide the below details: 1. Please update your Chrome to latest #66.0.3359.158 and let us know your observations. 2. If the issue is still observed, please share the screen cast of the issue. 3. Share the sample HTML file or test case or URL of the website to reproduce the issue at our end. 4. Share the device details on which the issue is reproduced. Thanks in advance!
,
Jun 1 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 1 2018
pnangunoori@ after recent investigation for this bug, I have following results: 1. This bug exists on latest build of Chrome. 2. This bug has no relationship with the web site or the HTML file 3. This bug at least exists on Samsung Galaxy S7 and Samsung Tablet S3(SM-T820). 4. The steady repro step is a) Provision an android device (https://github.com/googlesamples/android-testdpc). b) Launch testDPC, and allow default launcher in lock task mode. c) Call startLockTask() in onResume() of the default launcher(So you need to build Launcher3 and add this code in it, then set it as default launcher in Settings). d) Restart the android device, don't manually unlock the lock screen, wait until the default launcher startup automatically. e) Add a website shortcut to desktop by Chrome. f) Click on the shortcut and you will see Chrome launched but don't open the website. 5. This issue is because when user has not dismissed the lock screen and the device entered lock task mode, KeyguardManager.inkeyguardrestrictedinputmode will always return true, no matter whether the lock screen has been dismissed or not.
,
Jun 1 2018
This issue seems to be out of TE's scope. Hence, adding the label 'TE-NeedsTriageHelp' for the further triage of the issue. Thanks!
,
Jun 13 2018
,
Jun 18 2018
Bernard, could you take a look and find a right owner for this?
,
Sep 8
Bulk edit: Moving back into the untriaged pool, as I'm leaving the project.
,
Sep 19
Removing Enterprise as this is just basic "fire an intent to load a URL" functionality. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by kkaluri@chromium.org
, May 29 2018Labels: OS-Android