emm, just tried it with a tot chrome and it works. But somehow, it takes a very long time for the first run, about 2 minutes stuck in "Initializing app" phase. When I explore the app's profile dir, apps seems to be installed already. Maybe we lost some signal during first time install.

2nd time it runs normally (fast).

Probably caused by flaky network. StartupAppLauncher waits for network online before proceeding to install the primary app. After the primary app is installed, it will install the secondary apps. However, if network goes from online to offline, it bails out [1]. A possible fix could be add a way to retry/wait for network to recover.

[1] https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/chromeos/app_mode/startup_app_launcher.cc&l=511

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/35fa7b8dd3254770833edf5326ef24410b3613b1

commit 35fa7b8dd3254770833edf5326ef24410b3613b1
Author: xiyuan <xiyuan@chromium.org>
Date: Mon Apr 25 20:44:30 2016

kiosk: Install secondary app after DelayNetworkCall

Secondary apps install happens after network is configured. Wrap the
actual install call with DelayNetworkCall to avoid failure caused
by flaky network status.

BUG= 600878 

Review URL: https://codereview.chromium.org/1904323002

Cr-Commit-Position: refs/heads/master@{#389558}

[modify] https://crrev.com/35fa7b8dd3254770833edf5326ef24410b3613b1/chrome/browser/chromeos/app_mode/startup_app_launcher.cc

Xiyuan, what build will this fix be in?

Seems still not picked by today's canary, i.e. not in 52.0.2715.0. It looks like would be a build after 52.0.2717.0.

Will verify fix in M52 with 52.0.2717.0. We'll likely need to merge fix back to M51 and M50 thereafter.

fix verified in Chell, chromeos M52 version 8249.2.0 52.0.2717.5