Actually, it seems that this affects some of our devices ASUS CN60 devices on Chrome 69 as well, though much less frequently. (And rebooting the device tends to let the user into the app on Chrome 69, where on 70 it won't).

Using the same build and hardware. I am not able to repro this issue. What application is configured for launch?

TelemetryTV Media Player:
https://chrome.google.com/webstore/detail/telemetrytv-media-player/nnegimaehopiaikjnpdpokceckcbdoef

I am not able to reproduce this issue with the application you provided. How many times does this issue happen?

Earlier this week, it was daily. We'd come into the office and have the waiting for application window screen showing.

Can we get logs from the device (turn on device reporting + log upload and attach the logs to the bug)?

Also, if you can file a feedback report that could be useful.

I observed something similar using a asus chromebox flashed with stable 11021.56. 0. I was trying to install a arc application and the install process was hanging on "waiting for application window" . I did a soft reboot, after waiting a few minutes the application was installed successfully on my device. Attaching logs

Deleted: debug-logs_20181112-143524.tgz 6.9 MB

debug-logs_20181112-143524.tgz 6.9 MB Download

According to the logs, the kiosk app (com.wonderanimals.chimerasim) was not found on Play Store. I also can't see such app in Play Store - is the name correct?

interesting. I had it pre installed on my OU It must of been removed from the play store. Let me attempt with another application.

I am not able to repro this issue using Asus ChromeBox CN60. I tried auto launching ARC applications and chrome extension.

I've been unable to repro the issue for a while now as well.

Tried to reproduce this issue using M71 Stable

jono@ - are you still seeing this issue?  Given that we're not able to reproduce in-house, we'll need logs from you to further debug what's going on.

we started having the issue here across various devices and i'm gathing info on on chrome versions, apps, etc.

Chrome OS here is 70.0.35.38.110 the only things that seem to fix it at the moment is a powerwash or pulling the app back, waiting 15-20 minutes and then pushing it back out.  

bumping this to P1 now, it has potential to reach P0 if we can't get it solved ASAP before new year.

Let's keep this issue focused on Chrome kiosk app failures, not Android apps.

Attaching logs from a customers support case.  Currently this is affecting their school district.

Deleted: drive-download-20181207T133821Z-001 (1).zip 4.5 MB

drive-download-20181207T133821Z-001 (1).zip 4.5 MB Download

I setup 5 devices(3 Kiosk devices, 2 chrome books) hoping to reproduce this issue. All devices are flashed with 70.0.35.38.110 stable and enrolled in our test domain. Devices used for testing are Panther,Buddy,Veyron-Tiger,Falco, and Kip. 

2 devices are connected via Ethernet(Tiger and Falco) the remaining 3 devices are connected via WiFi. All devices are configured to launch telemetry media player extension(nnegimaehopiaikjnpdpokceckcbdoef). I have tried launching different extensions as well, no abnormal behavior is observed with my devices.

@Comment 22 - I sent in logs from 3 different devices today along with the serial numbers, and OU info in a support ticket.  in our support ticket I have listed the apps we are having the issues with.  The fix seems to be power washing or pulling the kiosk app back waiting a little and then repushing it.  

@23,

Hi Noel, i'm the owner of your support ticket currently (Case#17714090).  I don't see any logs that were uploaded today in the case, can you confirm if they were sent?  I can add them to the bug here so the engineers can take a look.

@22,

Can you verify the setting that you were using to push the apps? Public session kiosk vs Kiosk etc?  I will also work on attempting to repro the issue on my end, but in case the we aren't able to repro it on our side, is there somewhere in the logs that we can look for that would give us insight into why the customer is experiencing this issue?

@24,
  I sent them over around 1:30 an attachment with each Serial number.
and we are only using kiosk not public session kiosk.  

I'd love to also know where to look and if you dont have the logs can i attach them here.

@25, 

Yes please provide them here, as they don't appear to be attached to the case. 

c#24
The applications were configured for auto launch using kiosk.

@25 will do in the AM
@27 not auto launch kiosk

c#28
> not auto launch kiosk

Are you saying not to auto launch the extension in kiosk mode?

c#22

Where can I find the list of applications you are having troubles with?

@29 correct they select apps from the lower left corner at the login screen. and I will attach the list in the am.

@29 my mistake, the bug was originally filed using application/extensions configured to launch in kiosk mode. I will try manually launching the applications tomorrow morning.

@31 i actually ran into a personally created kiosk app that was autolaunch that also failed but the bigger issue was my case.  I can send that extension id if you like, was just trying to focus on the case i submitted.

@32 Please file a separate bug

@34 no problem. 

@35, 

I will file the bug shortly.

Filed issue# 914637.

@37, thank you.the logs attached here are from the auto launch kiosk.  I can attach the other logs to the new issue.

What's the difference with crbug.com/914637 ?

@39 This bug is for the kiosk app to auto launch and the other one is launching the app from the login screen but both bugs have the same issue.

This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.