Skip to content

Fix debug device/web socket closing #2897

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

Merged
merged 1 commit into from
Jan 5, 2018

Conversation

TsvetanMilanov
Copy link
Contributor

When we close the websocket we have to destroy the device socket as well.
We need to wait the close event on the device socket instead of end.

Copy link
Contributor

@rosen-vladimirov rosen-vladimirov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do not merge until we have fixed the issue in runtime.

@zahhak
Copy link

zahhak commented Nov 29, 2017

@rosen-vladimirov Is there an issue in the other repo for that? Do we have update on this?

@TsvetanMilanov
Copy link
Contributor Author

@zahhak I created an issue -> NativeScript/ios-jsc#832 with some additional information.

@petekanev petekanev force-pushed the milanov/fix-debug-sockets-closing branch 4 times, most recently from 2ce0929 to 61103da Compare December 18, 2017 09:23
When we close the websocket we have to destroy the device socket as well.
We need to wait the close event on the device socket instead of end.
@mbektchiev mbektchiev force-pushed the milanov/fix-debug-sockets-closing branch from 61103da to 90fa4fe Compare January 4, 2018 15:39
@mbektchiev mbektchiev changed the base branch from master to release January 4, 2018 15:39
Copy link
Contributor

@mbektchiev mbektchiev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's merge it along with #3275 because they are needed for the latest debugging improvements in ios-runtime

Copy link
Contributor

@Mitko-Kerezov Mitko-Kerezov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Issue in ios runtime has been resolved already, I think it's high time we merge this

@mbektchiev mbektchiev merged commit b27a519 into release Jan 5, 2018
@mbektchiev mbektchiev deleted the milanov/fix-debug-sockets-closing branch January 5, 2018 07:11
mbektchiev pushed a commit that referenced this pull request Jan 5, 2018
When we close the websocket we have to destroy the device socket as well.
We need to wait the close event on the device socket instead of end.
dtopuzov pushed a commit that referenced this pull request Jan 10, 2018
* Generate debug port in range for Chrome DevTools websocket - iOS (#3275)

* fix generating port for debug socket when debugging ios with chrome devtools

When generating a port to start a websocket on, use the same logic as is present in the android debug service - get the first available available port in a range, and reuse it for the next debug session of the same application if it is still available

* fix(device-socket): iOS Socket proxy should listen on IPv4 localhost adapter

Check for available port is done on this adapter and by default server is launched on "::" which is IPv6's any adapter

* Fix debug device/web socket closing (#2897)

When we close the websocket we have to destroy the device socket as well.
We need to wait the close event on the device socket instead of end.

* fix(ios-inspector): Correctly update cached inspector package to latest compatible version (#3302)

* Currently it is never updated and is left at the first version ever installed in `~/.local`.
As a result newly published inspector packages are not used unless the user installs
them explicitly in the project or deletes the cache manually.
* The iOS inspector package version must be determined according to project's iOS runtime
version instead of the version of CLI as it has been till now
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants