20

I have a Chrome application that experiences issues only when being run in kiosk mode. Is there any way to connect a debugger or enable the inspector for Kiosk-mode applications?

Simon Steele
  • 11,558
  • 4
  • 45
  • 67
  • I have the same problem but more specific, the problem occurs when running the app in Kiosk mode on a specific ChromeBox. Is there a way to connect a debugger, write remote log statements or visualise logging info on the device itself? – Bob Groeneveld Dec 12 '14 at 13:15
  • 1
    possible duplicate of [How to debug a Kiosk Chrome application running on a Chromebox?](http://stackoverflow.com/questions/27444971/how-to-debug-a-kiosk-chrome-application-running-on-a-chromebox) – Simon Steele Jan 20 '15 at 16:55

1 Answers1

19

If you run Chrome with the --remote-debugging-port=9222 option it will provide access to DevTools at http://localhost:9222/. If you need to access it from a different computer you can forward the port with ssh.

Source: http://blog.chromium.org/2011/05/remote-debugging-with-chrome-developer.html

Reilly Grant
  • 5,590
  • 1
  • 13
  • 23
  • 1
    Thanks, this is useful, but I can't see how to apply it to the case of kiosk mode on a ChromeOS device (i.e. a true kiosk). – Simon Steele Dec 18 '14 at 08:02
  • 2
    I provided a more detailed answer to Bob Groeneveld's question here: http://stackoverflow.com/questions/27444971/how-to-debug-a-kiosk-chrome-application-running-on-a-chromebox/27454778 – Reilly Grant Dec 19 '14 at 08:47