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 command broken with using --watch #2150

Closed
NathanaelA opened this issue Oct 21, 2016 · 2 comments
Closed

TNS run command broken with using --watch #2150

NathanaelA opened this issue Oct 21, 2016 · 2 comments
Assignees
Milestone

Comments

@NathanaelA
Copy link
Contributor

According to the docs (and my experience) with the tns run ios command -- it rebuilds the app, deploys it and then runs it.

However, if you add the cool magical --watch command the initial build/deploy is skipped and it acts exactly as if you did a tns livesync ios --watch. This is completely different behavior that I don't expect. When I use the tns run ios --emulator --watch I expect it do a full build the app, deploy it, run it and then livesync any changed files after that point.

Right now because it is broken; you have to a tns run ios --emulator ctrl-c after it deploys it, and then start the --watch command.

TNS v2.30 - issue is on ios for sure. No idea on Android as I still use my LiveEdit and never use the --watch command on android.

@tzraikov tzraikov added the bug label Oct 21, 2016
@tzraikov
Copy link
Contributor

Yes, I confirm that currently tns run ios --watch is just a shortcut for tns livesync ios --watch. Livesync works like this: it checks whether there is an app with the same id installed on the specified emulator/device. If so, it uses the app and transfers application files without rebuilding. If there is no application with the specified id deployed, livesync builds and deploys the app. However, calling build every time when executing run will mimimize the benefits of using livesync. That is why we will investigate this scenario further and we will try to find the best option.

@NathanaelA

This comment was marked as abuse.

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

No branches or pull requests

3 participants