Monthly Archives: July 2015

NativeScript v1.2.0 Built in LiveSync vs the NativeScript-LiveSync Plugin

Pros of Telerik's LiveSync:

  • Works from the NativeScript Command Line
  • No extra code added to your application!
  • Possibly works on Real IOS Devices (Untested on real device, but does not currently appear to work on a IOS Simulator)

Cons of Telerik's LiveSync:

  • Not really Live. It syncs the files; but then has to restart the application from scratch, no matter what file is changed.
  • Delays while it detects any changes and then deploys the changes.
  • Delays while it is re-launching Application.
  • Loss of all application state since it reloads the app on every change.
  • If you navigated three screens deep, and make a CSS file change; you will need to re-navigate to that screen again to see it.
  • Incredibly slow LiveSync startup time. (What in the world is it doing for about a minute?)
  • Can crash the LiveSync watcher code easily (don't change any files in the tns_modules!).
  • Does not apparently detect any new files...
  • Reset of the Application even if you change a file that isn't even being used.
  • Easy to crash your application as the JavaScript and XML are not checked before being sent to the application.

Con's of Master Technology's LiveSync:

  • Until Telerik accepts the patch; you have to use the included patched runtime. (Please vote up the issue!)
  • Added coded to your project.
  • Only works on the Android platform, no IOS support.

Pro's of Master Technology's LiveSync:

  • Live, You see the app change almost exactly when your editor saves the files.
  • New files are detected and synced instantly.
  • Application state is almost always fully maintained.
  • The screen you are working on only reloads ONLY if it is the code you just changed.
  • Built in ability to detect errors in XML and JS before pushing to device to eliminate crashing the app on the device.
  • Ability to only reload application on files that are singletons or other files that you would rather have the app reloaded for.
  • Ability to restart application by touching or creating a "restart.livesync" file.


The new LiveSync code has been updated to be a seemless installation on your Box.    It now includes the modified runtimes for v1.20 of the Android runtimes.     All you have to do to install it is: tns plugin add nativescript-livesync



NativeScript v1.20 Released

We all need to start upgrading,  Telerik has released v1.2.0 -- this is a important upgrade as it fixes several nasty bugs on IOS & Android!    It also adds a lot of cool new features.

1. To upgrade the command line: npm install nativescript -g

(On a mac or linux you might need a "sudo" in front)

2. To Upgrade the platforms: tns platform upgrade ios  or tns platform upgrade android

3. To upgrade the common modules; well that is still a pain.  I would advice you to follow the same instructions I had you follow in the v1.0.0 to v1.1.0 upgrade, however if you have manually added anything to your "tns_modules" (which I would not recommend you do, you will want to copy or re-install it in your new tns_modules)

cd ..
tns create testupgrade
rd /S /Q <strong>YOURAPP</strong>\app\tns_modules
move testupgrade\app\tns_modules <strong>yourapp</strong>\app
rd /S /Q testupgrade


First things first, NativeScript command line plugin code works a lot better.    You can now do:

tns plugin add android <somepluginname> and it works!

For those interested; my LiveSync plugin has already been updated for v1.2 with a slew of new features and a very simple install using the new tns plugin add android nativescript-livesync command.

Lots of new Features and here are some of the changes:

New Features