New issue
Advanced search Search tips

Issue 899168 link

Starred by 5 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

remote debug no longer works for kiosk mode application (developer mode, enabled debugging features)

Reported by chrome-z...@zipow.com, Oct 26

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10895.78.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.120 Safari/537.36
Platform: 10895.78.0 (Official Build) stable-channel guado

Steps to reproduce the problem:
1. enable developer mode, enable debugging features
2. add --remote-debugging-port=9222 to /etc/chrome_dev.conf
3. start kiosk mode application on ASUS Chromebox CN62 (enterprise enrolled, app set to auto launch)
4. try use remote debugging with Chrome DevTools on a Windows machine

What is the expected behavior?
remote debugging is OK as previous Chrome OS 67.0

What went wrong?
I can see the application's window listed in https://localhost:9222 page, when I click it, nothing appears, looks like the DevTools is disabled

Did this work before? Yes 67.0

Chrome version: 69.0.3497.120  Channel: stable
OS Version: 10895.78.0
Flash Version: 

related with new policy DeveloperToolsAvailability?
Can't enable it on admin console for kiosk mode, while it can be enabled for public session mode.

remote debugging for kiosk app is very important for developers, please give a solution ASAP
 
Owner: jarhar@chromium.org
Cc: jarhar@chromium.org
Owner: dgozman@chromium.org
Cc: -jarhar@chromium.org pmarko@chromium.org dgozman@chromium.org poromov@chromium.org
Owner: atwilson@chromium.org
I do think this is DeveloperToolsAvailability kicking in.

Over to atwilson@ and pmarko@ (who is OOO currently) to figure out whether this is a scenario we care about. Also +poromov@ from kiosk side of things.
Cc: aghuie@chromium.org dkalin@google.com atwilson@chromium.org
Owner: maxkirsch@chromium.org
reassigning to max to figure out what DeveloperToolsAvailability flag we should pass down to kiosk sessions (either change the default, or expose this to admins to select).
 Issue 908208  has been merged into this issue.
Components: -Platform>DevTools UI>Shell>Kiosk
any update?
I added --remote-debugging-port=9222 to etc/chrome_dev.conf

and followed the instruction here to try and initialize remote debugging

https://chromedevtools.github.io/devtools-protocol/

my kiosk application is not showing up under Apps tabs.  Am I missing something with my setup?

 Issue 910353  has been merged into this issue.
@vaandres

If you follow the steps I laid out in my issue (https://bugs.chromium.org/p/chromium/issues/detail?id=908208 - got merged into this one), you should be able to replicate.
Status: Assigned (was: Unconfirmed)
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.
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.
@atwilson, how sure are you that setting this policy will resolve the issue?

Sign in to add a comment