Skip to content

[Sporadic] Unable to start iOS debugger from VSCode extension #3821

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Fatme opened this issue Aug 15, 2018 · 1 comment
Closed

[Sporadic] Unable to start iOS debugger from VSCode extension #3821

Fatme opened this issue Aug 15, 2018 · 1 comment
Milestone

Comments

@Fatme
Copy link
Contributor

Fatme commented Aug 15, 2018

Tell us about the problem

Sometimes {N} CLI is not able to start iOS debugger from VSCode extension.

Which platform(s) does your issue occur on?

iOS

Please tell us how to recreate the issue in as much detail as possible.

Steps to reproduce:

  1. Create project and open it with VSCode extension
  2. Run Launch on iOS from VSCode extension
  3. An error is thrown:
    Error: Cannot connect to device socket. The error message is NativeScript debugger was not able to get inspector socket port. at Errors.fail (/usr/local/lib/node_modules/nativescript/lib/common/errors.js:125:28) at Errors.failWithoutHelp (/usr/local/lib/node_modules/nativescript/lib/common/errors.js:135:21) at SocketProxyFactory.<anonymous> (/usr/local/lib/node_modules/nativescript/lib/device-sockets/ios/socket-proxy-factory.js:91:38) at Generator.throw (<anonymous>) at rejected (/usr/local/lib/node_modules/nativescript/lib/device-sockets/ios/socket-proxy-factory.js:5:65) at <anonymous>
@Fatme Fatme added this to the 4.2.2 milestone Aug 15, 2018
@nickcabral
Copy link

I'm still getting this exact error after updating to CLI 4.2.2. Possible to reopen this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants