Issue with Chrome App Builder creating app that launches website in kiosk mode

TechInTheWoods
TechInTheWoods used Ask the Experts™
on
Full disclosure: not a developer, never worked with any of this before. This seemed like a very straightforward process that isn't working for some reason.

Trying to use Chrome App Builder : https://chrome.google.com/webstore/detail/chrome-app-builder/ighkikkfkalojiibipjigpccggljgdff?hl=en
To create an app that points to a website that will run in kiosk mode. This should be a relatively simple undertaking. You name the app, plug in the url in the homepage section, (our is https://ffc-ic.ffc8.org/campus/OLRLoginKiosk/ffc) configure any settings for navigation, then select to save as kiosk.

While testing the app by opening the more tools-->extensions-->turn on developer mode-->load unpacked, however, I get errors. Having no idea where to even start on this (isn't it just supposed to be redirecting to a website?) I'm asking for assistance to determine where the errors could possibly be coming from.

Warning: Unknown Model in arequire
function arequire(modelName, opt_X) {
  var X = opt_X || GLOBAL.X;
  var model = FOAM.lookup(modelName, X);
  if ( ! model ) {
    if ( ! X.ModelDAO ) {
      console.warn('Unknown Model in arequire: ', modelName);
      return aconstant(undefined);
    }

Open in new window


Warning: Tried to load
arequire(obj.model_)(function(model) {
            if ( ! model ) {
              console.warn("Tried to load ", obj.model_, " on demand, but no luck.");
              future.set(obj);
              return;

Open in new window

Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2016

Commented:
Are you aware of the following As of 21 November 2016, all newly published packaged or hosted apps are restricted to Chrome OS, and are not available to users on Windows, Mac or Linux.

Author

Commented:
@David Johnson

Yes, thanks. I'm testing on a Chromebook.
Wow-talk about a red herring. It turns out that the error/warning events I was seeing had absolutely nothing to do with why the app was not working. Our content filter was blocking "jabber" and a number of non-standard port/IP address combinations from Google. Once I added the list of them to be allowed, the app functioned as it should!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial