Kiosk mode app fails to launch with "Kiosk Application could not be downloaded" error |
|||||
Issue descriptionChrome Version: Chrome OS 57.0.2987.146 OS: ChromeOS What steps will reproduce the problem? 1. Configure a ChromeBook to Auto-Launch a Kiosk App 2. Turn on any new device or affected device. What is the expected result? Auto-Launch the configured App What happens instead? Shows an error message on the screen “Kiosk App could not be downloaded.” the customer was trying to use the StratosMedia Player as a Kiosk App https://chrome.google.com/webstore/detail/stratosmedia-player/alhlkpgheiefedomljbenmkpconkffhk Time of the problem: around 10:31
,
Apr 27 2017
,
Apr 27 2017
Saw these in the log: [2355:2355:0426/103152.293019:WARNING:safe_manifest_parser.cc(75)] Error parsing update manifest: Entity: line 1: parser error : Specification mandate value for attribute async omljbenmkpconkffhk"/><script src="https://apis.google.com/js/platform.js" async Last time we saw this, the admin used CWS details url (https://chrome.google.com/webstore/detail/...) as the update url for a kiosk app in cpanel. This might be the case here. binzhao@, we should probably make cpanel black list this detail url since it looks like a common mistake.
,
May 3 2017
Hi Bin, Xiyuan can you please advise where does device store cws details url for kiosk apps? So will help us to check how customer are configured it. (checked, not inside .manifest or other file in home/chronos/kiosk/crx/......omljbenmkpconkffhk.crx)
,
May 4 2017
The update URL is part of device policy. It is the URL field when admin adds the kiosk app via "Specify a Custom App" in cpanel. The field should either by empty or "https://clients2.google.com/service/update2/crx", unless the admin has a private server to provide the crx.
,
May 11 2017
We have the policy of the customer, and as you were saying it's the wrong url. thank you.
,
May 11 2017
Thanks for checking. Won't fix then since it is a policy config error. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by marcore@chromium.org
, Apr 27 2017