The issue seems to be related to OS-chrome. Hence, adding appropriate OS labels.

Thanks...!!

We are also seeing this. I kind of suspect new apps can't be unmanaged kiosk anymore. Only some existing apps that were grandfathered in since there was the move for chromebook after 2017 allowing kiosk only if managed. But I find no documentation stating that.

We are also experiencing the same issue. Our app runs fine in the kiosk mode on managed devices, thus, we concluded that it is not a publishing or build error. 

According to the article (https://support.google.com/chromebook/answer/3134673?hl=en)  "kiosk mode" policy change will effect only chrome OS devices build after 2017. I agree, there is no supporting documentation stating that newly developed apps will be prevented from running in kiosk mode on older unmanaged devices.

Please let us know if there is a resolution for this issue. We are building apps for k-12 and one of our requirements is to support kiosk mode on unmanaged device build prior 2017.

Thank you!

I was able to reproduce this issue that youre facing. I put one of my kiosk device in consumer kiosk mode, and I published an chrome extension in the store 08/22/2018. Once I retrieved the app ID, I tried to install my new extension via chrome://extensions > Manage Kiosk Applications. I got the same error message "Invalid Application ID"

Unfortunately I was unable to find a resolution despite researching and testing different manifest.json changes. Luckily our kiosk requirements were minimal so I was able to find a different resolution. For those interested, I recommend reloading the Chromebox to run Porteus Kiosk (http://porteus-kiosk.org/) a linux based Kiosk OS. As far as a resolution goes for chrome kiosk apps, I am still awaiting an answer. Thank you.

Encountering the same issue with: https://chrome.google.com/webstore/detail/kiosk/afhcomalholahplbjhnmahkoekoijban?hl=en

If this is not a bug, public documentation stating this feature has been removed would be beneficial. We have quite a few confused users.

Deleted: KioskApp.png 136 KB

	KioskApp.png 136 KB View Download

The colleagues above are not alone with the frustration. Please fix and/or document

As of this weekend we're seeing the same problem with our kiosk app. We getting many reports from customers who have bought a Chromebit or Chromebox to run our kiosk app, but cannot install it anymore. I'm assuming this has to do with Google's new policy to only allow kiosk apps to run on enterprise managed devices (https://support.google.com/chromebook/answer/3134673?hl=en&vid=0-542325946619-1537256023576). But that is completely not an option for our customers: they just want to have a device that auto-starts our (digital signage) app (which is just a webview component) in full screen mode on startup. 95% of them don't need and even don't *want* device management features and all the additional complexity. 

If there is a way to get a browser to autostart in fullscreen mode when the power comes on, which doesn't involve kiosk mode, then I'm desperate to hear about out. Because with this issue (and possible this policy), ChromeOS has effectively become useless for almost all of our customers.

Kiosk app problem started last week on 09-13-18, was hoping it was a temporary issue and would be fixed. 
 We use your chrome kiosk application on a CHROMEBOX.   We have used the kiosk application on over 100 installations.  In the last week, I am setting up kiosk auto launch and when I get to chrome://extensions  I then go down to Kiosk 
and copy the application id then I click the manage kiosk application
Then where it says enter application id I paste it
Now since last Thursday 09/13/18 I am getting invalid application.

I have reset 2 chromeboxs 5 times each to start completely over and have received the same error message over the last 3 working days.

I hope there will be a quick resolution to the KIOSK/CHROME problem. 

I find the lack of communication on this issue troubling. We're seeing this same problem as well and it's becoming a major issue for us. 

+sergey since you are looking at the related bug (probably dupe the two together).

pas...@lindelauf.com this is the exact issue that we have. I have ~1,500 devices in the field that just display a simple URL hosted on a local machine. No keyboard or mouse attached, no touch screen, no user interaction with the system, no real "kiosk." They use a kiosk extension because that's the only way to get them to auto launch and display the URL full screen.

It seems Google is effectively holding Chrome based digital signage hostage now.

Please, share your kiosk app IDs. It will really help debugging.

Kiosk 5.18.0

afhcomalholahplbjhnmahkoekoijban

https://chrome.google.com/webstore/detail/kiosk/afhcomalholahplbjhnmahkoekoijban