search

NathanaelA / nativescript-liveedit

Live Edit of your NativeScript project while developing it
MIT License
38 stars 3 forks source link

Application crashes #13

Open dragGH102 opened 8 years ago

dragGH102 commented 8 years ago

I run 

  npm install jshint -g
  tns plugin add nativescript-liveedit

Then node watch in another terminal, uninstalled the app and added the following code to my app.ts:

   [....]
  var liveedit = require("nativescript-liveedit" );
  liveedit.debugMode(true);
  application.start();

Result: 'the app has stopped' (on emulator)

Output of terminal with node watcher running on:

Pushed to Device: Pushed to Device: .... Pushed to Device: ... Starting application... Starting application... Starting application...

NathanaelA commented 8 years ago

Did you rebuild the app via a tns run or tns deploy?

dragGH102 commented 8 years ago

yes via tns build

On Wed, Jan 13, 2016 at 5:59 PM, Nathanael Anderson < notifications@github.com> wrote:

Did you rebuild the app via a tns run or tns deploy?

— Reply to this email directly or view it on GitHub https://github.com/NathanaelA/nativescript-liveedit/issues/13#issuecomment-171363922 .

Manuel Gajo Full-stack web Developer and Business Designer www.manuelgajo.me http://www.manuelgajo.me +39 333 623 4217 / +32 484 369 265

IMPORTANT: My e-mail is personal and PRIVATE and CAN'T be shared with any third party company or organisation without my explicit authorisation.

NathanaelA commented 8 years ago

tns build won't deploy it to the emulator/device. So you won't be running the plugin on the device. You need to do a tns deploy or tns run so that the plugin and new runtimes get deployed to the device. My personal work flow on a new project is: tns plugin add nativescript-liveedit tns run android --emulator --geny x (Start watcher in another shell/cmd window) Start editing my code and letting the watcher keep things in sync on the device/emulator.

The next morning (or if I kill the emulator); I just do another tns run android --emulator again so that it starts up. I happen to like the limited console output that tns run provides. So I use it to start when I start working on the project again. But I let the nativescript-liveedit keep everything in sync.

NathanaelA commented 8 years ago

One note; anytime you add any new plugins or change any files in the app_resources folder; you need to do a tns run/tns deploy once to get everything resynced. Neither my liveedit nor the built in livesync will sync app resources or plugins.

dragGH102 commented 8 years ago

the fact is that it gives me the issue even with deploy. However I'll eventually try it again later on. In fact, besides not re-compiling assets automatically, livesync has the only big limitation to force me (most times) to re-build everything if an error occurs.

On Wed, Jan 13, 2016 at 7:56 PM, Nathanael Anderson < notifications@github.com> wrote:

One note; anytime you add any new plugins or change any files in the app_resources folder; you need to do a tns run/tns deploy once to get everything resynced. Neither my liveedit nor the built in livesync will sync app resources or plugins.

— Reply to this email directly or view it on GitHub https://github.com/NathanaelA/nativescript-liveedit/issues/13#issuecomment-171397349 .

Manuel Gajo Full-stack web Developer and Business Designer www.manuelgajo.me http://www.manuelgajo.me +39 333 623 4217 / +32 484 369 265

IMPORTANT: My e-mail is personal and PRIVATE and CAN'T be shared with any third party company or organisation without my explicit authorisation.