20

Trying to run a Nativescript debug session and every time I enter

chrome-devtools://devtools/bundled/inspector.html?experiments=true&ws=localhost:41000

it opens a google search rather than the debug session.

https://www.google.com/search?q=chrome-devtools%3A%2F%2Fdevtools%2Fbundled%2Finspector.html%3Fexperiments%3Dtrue%26ws%3Dlocalhost%3A41000&oq=chrome-devtools%3A%2F%2Fdevtools%2Fbundled%2Finspector.html%3Fexperiments%3Dtrue%26ws%3Dlocalhost%3A41000&aqs=chrome.0.69i59j69i60j69i61.1074j0j7&sourceid=chrome&ie=UTF-8

Any ideas how to fix this please.

MrWrighty
  • 203
  • 1
  • 2
  • 4
  • 1
    Which version of Chrome you are using? Are you on Mac? Try replacing chrome-devtools with devtools in the url. – Manoj May 28 '20 at 14:22
  • The `chrome-` prefix was removed in https://crrev.com/748242 – wOxxOm May 28 '20 at 14:37
  • Thank you for that, I hadn't realised. Begs the question why, when running tns debug, we are still told to use chrome-devtools://devtools/bundled/inspector.html?experiments=true&ws=localhost:41000 to open a debug session. – MrWrighty May 28 '20 at 14:43
  • The reason why, is because this was a change in Chrome 83, which was just released and not everyone has upgraded to 83 yet. I'm sure the url will be fixed in a future version of tns. – Nathanael May 30 '20 at 18:27

4 Answers4

28

The URL scheme was recently changed to just devtools:// in chromium. The NativeScript CLI v7 has been rereleased to correct this minor change.

Use devtools://devtools/bundled/inspector.html?experiments=true&ws=localhost:41000.

Ian MacDonald
  • 13,472
  • 2
  • 30
  • 51
20

I was faced with the ERR_INVALID_URL when i tried with @IanMacDonalds answer.

For some reason navigating to the URL without parameters first, loaded devtools properly.

devtools://devtools/bundled/inspector.html

Then adding the params on afterwards got the debugging session working again.

?experiments=true&ws=localhost:40000

Hope that helps @Przemo

Radiohe4d
  • 201
  • 1
  • 4
0

You can use devtools://devtools/bundled/inspector.html?experiments=true&ws=localhost:40000 in Opera Browse, works fine

0

Opening an inspector on a random website, and then opening the Nativescript inspector fixed it for me since the latest Chrome release.

Tom
  • 98
  • 1
  • 4