unexpected server response (400) about vscode-edge-debug HOT 12 CLOSED

Is your page already running? From the list it looks you have the start page and MSN to attach to. If you have just your page open that you want to attach to that should work better. Or, you can add a url property to your config with the exact (there is no fuzzy matching) URL in the browser that you want to attach too.

from vscode-edge-debug.

Now i have this error: [debugger-for-chrome] unexpected server response (400)

from vscode-edge-debug.

Yay progress :).

Could you add the setting "diagnosticLogging": true to your launch.json's attach section and see if that gives any more error details that you can paste here.

from vscode-edge-debug.

OS: win32 ia32
  ›Node version: v5.10.0
  ›Adapter version: 0.0.5
  ›initialize({"adapterID":"edge","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true})
  ›attach({"name":"Launch localhost with sourcemaps","type":"edge","request":"launch","url":"http://localhost/my.html","webRoot":"c:\\Users\\Malte\\Desktop\\Edge","sourceMaps":true,"diagnosticLogging":true,"noDebug":false,"port":9222})
  ›Attempting to attach on port 9222

  ›Adapter error: Error: Command failed: C:\Users\Malte\.vscode-insiders\extensions\msjsdiag.debugger-for-edge-0.2.0\node_modules\edge-diagnostics-adapter\dist\x64\EdgeDiagnosticsAdapter.exe --port=9222 --launch=http://localhost/my.html
[2016-04-26 20:43:42] [error] Handshake ended with HTTP error: 400
  ›From client: disconnect({"restart":false})
  ›To client: {"seq":0,"type":"response","request_seq":3,"command":"disconnect","success":true}

from vscode-edge-debug.

Thanks. Could you try running from a console window:
C:\Users\Malte\.vscode-insiders\extensions\msjsdiag.debugger-for-edge-0.2.0\node_modules\edge-diagnostics-adapter\dist\x64\EdgeDiagnosticsAdapter.exe --chrome from the command line then navigate to localhost:9222 and click on the page you want to debug. Then hopefully they'll be some more detailed info in the console. Ideally if you navigate to localhost:9222 from Chrome.

from vscode-edge-debug.

I updated the title of the issue to reflect the bug a bit better.

from vscode-edge-debug.

@Nalyienf random question: are you using a version of Windows that isn't en-us?

from vscode-edge-debug.

Yes and the console option doesnt work.
I tried the option "Launch localhost with sourcemaps". ( I use XAMPP) Edge is opening the side but in the console is an error: ›Warning: Can't find a page with url: http://localhost/index.html. Available pages: ["unknown"] and on the top of VSCode [debugger-for-chrome] unexpected server response (400)

I tried it also with the Chrome Debugger an all worked fine.

from vscode-edge-debug.

Ahh yea I think the issue is:
microsoft/edge-diagnostics-adapter#19

Basically that the ACL isn't being applied to the folder in non-English builds.

from vscode-edge-debug.

It worked with "Launch localhost with sourcemaps"
THANK YOU ! :)

from vscode-edge-debug.

Only when i debug with "Launch index.html" i get an error [debugger-for-chrome] Got response from target app, but no valid target pages found.

But with the chrome debugger this option works.

from vscode-edge-debug.

That error means that the URL in the launch.json doesn't match the URLs that are open in the browser. I'm going to close this issue as the issue should be fixed. If you have problems launching please do open a new issue with more details :). Thanks for trying it out!

from vscode-edge-debug.