Skip to content
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

fix(ios-inspector): Update cached inspector package to latest compatible version #3302

Merged
merged 1 commit into from
Jan 8, 2018

Conversation

mbektchiev
Copy link
Contributor

@mbektchiev mbektchiev commented Jan 5, 2018

  • 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

@mbektchiev mbektchiev added this to the 3.4.1 milestone Jan 5, 2018
@mbektchiev mbektchiev self-assigned this Jan 5, 2018
@mbektchiev mbektchiev force-pushed the bektchiev/fix-inspector-cache-update branch 3 times, most recently from 97b804d to 62b24c7 Compare January 8, 2018 09:26
@@ -10,6 +10,7 @@ import * as StaticConfigLib from "../lib/config";
import * as yok from "../lib/common/yok";
import ChildProcessLib = require("../lib/common/child-process");
import { SettingsService } from "../lib/common/test/unit-tests/stubs";
import { ProjectDataService } from "../lib//services/project-data-service";
Copy link
Contributor

Choose a reason for hiding this comment

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

../lib//services/ should be ../lib/services/

…st compatible version

* 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
@mbektchiev mbektchiev force-pushed the bektchiev/fix-inspector-cache-update branch from 62b24c7 to 525348f Compare January 8, 2018 11:04
@mbektchiev mbektchiev merged commit 8cc23e4 into release Jan 8, 2018
@mbektchiev mbektchiev deleted the bektchiev/fix-inspector-cache-update branch January 8, 2018 16:17
mbektchiev pushed a commit that referenced this pull request Jan 9, 2018
…st 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
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
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants