tns run ios shows "no reachable hosts" after running unit tests

[jschwartz73]

After running unit tests via

• tns test ios

a call to

• tns run ios

displays an app with a big image of "N" and a label that says "no reachable hosts"

My expectation is that the app would run (not the unit tests)

tns info
nativescript │ 3.2.1 │ 3.2.1 │ Up to date │
tns-core-modules │ 3.2.0 │ 3.2.0 │ Up to date │
tns-android │ │ 3.2.0 │ Not installed │
tns-ios │ 3.2.0 │ 3.2.0 │ Up to date │

Steps to reproduce:

1. tns create test-app
2. cd test-app/
3. tns run ios
4. tns test init # Choose Jasmine
5. tns test ios
6. tns run ios

Any help would be greatly appreciated.

[jschwartz73]

[jschwartz73]

I have now reproduced this on two computers.

[NickIliev]

@jschwartz73 try the suggestions below

This could be caused by several things

During execution of tests, CLI changes the entry point of an application. After that, when tns run is executed, the original file should be transferred.
I see two options here:

1. tns test <platform>; tns run <platform> - the second one should prepare the project and restart app on device. We may have issues with checking if app should be prepared and we may have skipped it. This will reproduce the issue
2. The other option is that tns run <platform> had synced correct files, but without the app/package.json

The workaround should be pretty easy - touch app/package.json and execute tns run <platform> after that.

[jschwartz73]

I tried the workaround and it does not solve the issue.

Any other suggestions?

[wfwheele]

@jschwartz73 I was experiencing the same thing, it looks like running the tests might have changed app/package.json which I believe is how tns run ios figures out how to start the application. For me I could see via git status that it was modified and just did a git checkout -- app/package.json

Basically you need to make that file looks something like this

{
  "android": {
    "v8Flags": "--expose_gc"
  },
  "main": "main.js",
  "name": "tns-template-hello-world-ng",
  "version": "3.1.2"
}

In your case I bet main points to the unit test runner and not the app itself.

Could anyone give some info on when that file gets changed and whether or not it should or shouldn't be in version control?

[rosen-vladimirov]

Hey all,
tns test <platform> command must update the package.json inside <platforms> dir only - that's how the tests are run. However, it looks like there is some issue with this and it updates the entry point in your app/package.json. This is definitely not intended. Can all of you, who hit the issue, share the following information:

• npm version (output of npm -v):
• Node.js version (output of node -v):
• Xcode version (output of xcodebuild -version):
• Do you reproduce the issue with iOS or Android:
• Do you have local plugins, do you use npm link in your development workflow?

Meanwhile, I've reproduced and confirmed that the following workflow does not work:

• tns run ios
• tns test ios
• tns run ios - at this point CLI prints Skipping prepare and does not update package.json in platforms dir, so the application running on device is the one with tests. CLI should not skip prepare here.
  The workaround for this issue is to execute touch app/package.json and run tns run ios again. This will force CLI to prepare the application.

[wfwheele]

@rosen-vladimirov as per request:

npm -v : 5.4.2

node -v : v8.1.3

xcodebuild -version : Xcode 9.0 Build version 9A235

I've only been developing with iOS thus far as the project I'm working on only requires iOS at this time.

No local plugins, just a vanilla install using the cli.

[jschwartz73]

npm -v: 5.4.2
node -v: v6.11.3
xcodebuild -version: Xcode 9.0, Build version 9A235

I can reproduce the problem every time using these steps:

1. tns create test-app
2. cd test-app/
3. tns run ios
4. tns test init # Choose Jasmine
5. tns test ios
6. tns run ios

I'll film a short screencast to demonstrate

[jschwartz73]

https://s3.amazonaws.com/schwartech/nativescript-cli-3146.mov.zip

@rosen-vladimirov Hi. I got the same issue reproduced on Android. Steps are the same as for iOS

npm -v: 5.3.0
node -v: v8.6.0
xcodebuild -version: Xcode 9.1, Build version 9B55

[henriqueadonai]

NPM -V = 5.5.1
Node -v = v8.9.1
Using Windows/Visual studio code
ANDROID

[jschwartz73]

I'm now running:
npm -v: 5.4.2
node -v: v6.11.3
xcodebuild -version: Xcode 9.1, Build version 9B55
iOS only for the time being