note to Rohit: this is a bug in the app in test, not the release app

Also this appears to be specific to the Pixel 1. Could not repro on two other CrOS devices. 

ajnolley@ feel free to mark it as a blocker if needed.

ajnolley@, what is "CRD"? Simply the Chrome browser version on your host/client? Could you specify the build version on the Pixel 1? Also, if we wanted to try a repro, would we be able to access the test web app? 

vsuley: CRD is Chrome Remote Desktop. Since we have our own release process, the web app is still in test and has not been released to the public. However, if you would like to confirm the issue, the URL for the web app is: https://pantheon.corp.google.com/m/cloudstorage/b/chrome-unsigned/o/desktop-5c0tCh/57.0.2987.84/precise64/remoting-webapp.v2.zip.

The build version info is:
Google Chrome	58.0.3027.0 (Official Build) dev (64-bit)
Revision	0
Platform	9331.0.0 (Official Build) dev-channel link
Firmware Version	Google_Link.2695.1.169

AJ, does the M57 webapp on ChromeOS connecting to M57 Win10 host (with curtain mode) fail in the same way?

Does M57 ChromeOS webapp connecting to Win7 non-curtain mode have this problem?

Can you grab some client and host logs for the failure and send them to me?  It is tough to know why this is occurring otherwise.

Per discussion with AJ, this issue isn't a regression from the last release and can be reproduced with the M52 webapp and M56 host.

Reading through the attached log it seems like it might be signaling related as the client and host connect but then I see a bunch of channel negotiation and eventually a disconnect.

Deleted: Sawbuck.rtf 4.4 MB

Sawbuck.rtf 4.4 MB Download

From the log it looks like the host fails to to establish P2P connection.
AJ, can you please attach client logs?

After auto update, this issue no longer occurs. Closing