New issue
Advanced search Search tips

Issue 908208 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 899168
Owner:
Closed: Dec 5
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Remote debugging of chrome os kiosk applications is broken

Reported by jeff...@gmail.com, Nov 24

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36
Platform: 11021.81.0 (Official Build) stable-channel ninja

Steps to reproduce the problem:
1. Set up an AOPEN chromebox in developer mode
2. Enterprise enroll the device, and set the device to auto-start a kiosk application
3. Run the following commands to enable writing to the filesystem
 and auto-starting SSH:
`/usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification`
`reboot`

`/usr/libexec/debugd/helpers/dev_features_ssh`
`passwd`
4. Set the remote debugging port by adding "--remote-debugging-port=9222" to `/etc/chrome_dev.conf`
6. Restart the chromebox and let it load the specified kiosk application
6. Create an SSH tunnel into the chromebox by running the following command on your development machine:
`ssh -L9222:127.0.0.1:9222 root@<chromebox ip>`
7. Open the web browser on your dev machine and visit `http://127.0.0.1:9222/`
8. Select one of the pages to inspect

What is the expected behavior?
The chosen page should open successfully within devtools. We should be able to utilize dev tools on a chrome os app running in kiosk mode.

What went wrong?
Devtools opens with a completely blank page. No console commands can be run. No functionality within devtools works.

Did this work before? Yes not sure - probably around 54.x

Chrome version: 70.0.3538.110  Channel: stable
OS Version: 70.0.3538.110
Flash Version: 

Both the chromebox and the version of chrome running on my dev machine are 70.0.3538.110. I've already tried downgrading my version of chrome on my dev machine.

Being able to debug within kiosk mode with developer tools is ESSENTIAL to developing chrome os kiosk applications. Debugging within the OS as an unpacked extension does NOT yield the same results as running in kiosk mode. We have been trying to track down a memory leak within an application that does not exist when running the application as an unpacked extension (on Chrome OS, Windows, or Mac).
 
Screenshot 2018-11-24 05.02.36.png
137 KB View Download
Owner: dgozman@chromium.org
Status: Assigned (was: Unconfirmed)
If you open DevTools on DevTools, does it show any errors in the console?
The console has no errors when I open DevTools on the remote debugging DevTools
Mergedinto: 899168
Status: Duplicate (was: Assigned)

Sign in to add a comment