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

tns run/emulate/deploy does not check if device is available before build #1167

Closed
dtopuzov opened this issue Nov 10, 2015 · 1 comment
Closed
Milestone

Comments

@dtopuzov
Copy link
Contributor

Steps to reproduce:
run/emulate/deploy on not existing device/emulator/simulator

Result:
tns execute prepare and build and after that check if device is available.

Suggestion:
When execute un/emulate/deploy check if device/emulator/simulator before prepare and build.

@dtopuzov dtopuzov added this to the 1.6.0 (Under consideration) milestone Nov 10, 2015
@teobugslayer teobugslayer modified the milestones: 1.5.0, 1.6.0 (Under consideration) Nov 16, 2015
@vchimev vchimev closed this as completed Dec 1, 2015
@vchimev vchimev reopened this Dec 2, 2015
@vchimev vchimev removed this from the 1.5.0 milestone Dec 2, 2015
@vchimev
Copy link

vchimev commented Dec 2, 2015

Done for the run and deploy commands in 1.5.0.

If you execute tns emulate android --device xxxxx it starts the default emulator.
If you execute tns emulate ios --device xxxxx it prepares, builds and finally reports that Unable to find device xxxxx.

Closing this one and updating the relevant: #289.

vchimev pushed a commit to NativeScript/nativescript-cli-tests that referenced this issue Dec 2, 2015
@vchimev vchimev closed this as completed Dec 2, 2015
@vchimev vchimev added this to the 1.5.0 milestone Dec 2, 2015
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

4 participants