Hi Toni, can you please look into it?

On which initialization screen does the app hang (which message is displayed in the UI)?

I believe - during Kiosk mode start, it just displays "App is initializing.."

Correct, it just displays the attached image until it enters a sleep state, which is outside the policy control of kiosk settings.

Deleted: 20170417-2127.png 38.4 KB

	20170417-2127.png 38.4 KB View Download

And the message above the spinner remains "Please wait" through out?

Can you please remove the app from CPanel, restart the machine (confirm that no app is auto-launching and you are seeing the sign-in screen) and add the app back and let us know if you are still seeing the issue?

Thanks.

Yes, spins the entire time.

Would moving a device to an organizational level with no apps assigned, and remotely restarting the device suffice to confirm it ends up on the sign in screen?

You can keep the device in the same OU. You can remove the app, remotely restart and then add the app again. Let us know if that works.

I followed this process, and confirmed the app was wasn't loaded.

When adding the app back to the OU nothing changed. The device was not affected; authentication credentials and media assets were all still there.

The device also continued to show the same symptoms reported.

Can you please confirm that you removed the app? It looks like the app was not removed (based on your description that authentication credentials were retained)

I assume you did not configure your app in the root OU level. If so, can you please create a test-OU under root-OU and move one of the affected device there. Then, please go to guest mode, open the browser and type chrome://policy and click "Reload polices" - this is to confirm that the device received the new policies. When you reboot, the device should go to the sign-in screen.

Now, move the device back to original-OU, go to guest mode, open the browser and type chrome://policy and click "Reload polices" and let us know if WAND app is starting successfully.

In the meantime, can you send us your App-id with the app-specific configurations? We can try to repro the issue at our end. I assume this will require a pairing code (authentication credentials).

I had to recreate the issue locally to fully confirm and accomplish this request; since remote reboot and screen shot require an app assigned.

After removing the app entirely as requested, when adding the app back tot he device it immediately displayed the same symptom of the app hanging. I let it sit for half an hour and it never loaded. After rebooting through the management console it loaded.

Subsequent disconnecting power reboots hung the app, and it reported the same January 2013 date in the device logs.

Ok, can you send us your App-id with the app-specific configurations? We can try to repro the issue at our end. I assume this will require a pairing code (authentication credentials).

This is a chromebit specific issue, our app exists on any number of Chrome devices without issue.

I can send you an effected device via FedEx, or find an effected device and enroll it to an account you have access to.

I am perfectly willing to supply our app, but do not believe you will gain from that without the device in the correct state.

We weren't able to repro the issue with the Chromebits we have. We will try with a few more Chromebits. If not, we will let you know.

Also, can you please update the OS to the latest Stable and see if you are able to repro the issue? It looks like you are running M56. Can you please try running M57?

Toni, some addition information re: app initialization issue. It looks like it can easily be reproduced when the WiFi signal is flaky (as per a partner, they were able to repro the issue around -80dBs WIFI signal strength).

May be something related to retry logic during app initialization?