A Chrome Kiosk application that I wrote has a problem only when running in Kiosk mode on a Chromebox. When staring the application manually after I log into the Chromebox it runs well. Also when testing the application on my development machine everything works well.
How can I attach a remote debug session, write remote logging information or in any other way get debugging information from the Kiosk application on the Chromebox to my development machine?
Setting a kiosk app to launch automatically turns devices running Chrome OS into single-purpose devices. You can deploy multiple kiosk apps to devices, but you can only configure one app to automatically launch when devices start.
If you run Chrome with the --remote-debugging-port=9222 option it will provide access to DevTools at http://localhost:9222/
. Now, on a Chromebox running in Kiosk mode that's not all that useful (or even possible) without some extra steps:
/etc/chrome_dev.conf
.killall chrome
or pkill chrome
so that the command line changes take effect.ssh -L9222:127.0.0.1:9222 chronos@<chromebox ip>
http://localhost:9222/
Given all this it is easier to debug a kiosk app if you can run it unpackaged in non-kiosk mode.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With