NativeScript AppSync plugin
A live-update service for your NativeScript apps!
📣 NOTE: NativeScript AppSync is currently in beta and is not supported by the core NativeScript team. AppSync is based on Microsoft CodePush and we owe them thanks because this solution builds upon their work. ❤️
Optional reading: what this is, and how it works
The AppSync plugin helps get product improvements in front of your end users instantly, by keeping your code and images synchronized with updates you release to the AppSync server. This way, your app gets the benefits of an offline mobile experience, as well as the "web-like" agility of side-loading updates as soon as they are available. It's a win-win!
In order to ensure that your end users always have a functioning version of your app, the AppSync plugin maintains a copy of the previous update, so that in the event that you accidentally push an update which includes a crash, it can automatically roll back. This way, you can rest assured that your newfound release agility won't result in users becoming blocked before you have a chance to roll back on the server. It's a win-win-win!
Architectural overview of the solution - you don't need to worry about all of this
What can (and will) be AppSync'ed?
- Anything inside your
/appfolder (but not the
- Anything inside your
💁♂️ Note that we don't actually use those folders, but the
platforms/android/app/src/main/assets/app, the benefit of which is we don't "care" if you use Webpack or Uglify or whatever tools you use to minify or scramble your app's assets.
What can't (and won't):
- NativeScript platform updates. Example: bumping
tns-androidfrom version 2.5.1 to 2.5.2.
- Plugins updates that also require a different version of a native library it depends on.
- Contents of the
App_Resourcesfolder, because those are part of the native binary as well.
So as long as you don't change versions of dependencies and tns platforms in your
can push happily. And if you do bump a version of a dependency make sure there are no changed platform libraries.
Globally install the NativeScript AppSync CLI
npm i -g nativescript-app-sync-cli
💁♂️ This will also add the global
nativescript-app-synccommand to your machine. You can check the currently installed version with
Login or register with the service
Check if you're already logged in, and with which email address:
Log in if you already have an account:
Register if you don't have an account yet:
This will open a browser where you can provide your credentials, after which you can create an access key that you can paste in the console.
You should now have a
.nativescript-app-sync.config file in your home folder which will automatically
authenticate you with the server on this machine from now on.
Note that you could use a that web interface for managing you apps, but the CLI is much more sophisticated, so it's recommended to use the command line interface.
To log out, you can run
nativescript-app-sync logout which will also remove the config file.
To perform a headless login (without opening a browser), you can do:
nativescript-app-sync login --accessKey <access key>.
Register your app with the service
Create an app for each platform you target. That way you can roll out release seperately for iOS and Android.
appnamemust be unique, and should not contain dashes (
nativescript-app-sync app add <appname> <platform># examples:nativescript-app-sync app add MyAppIOS iosnativescript-app-sync app add MyAppAndroid android
💁♂️ This will show you your deployment keys you'll need when connecting to the AppSync server. If you want to list those keys at any later time, use
nativescript-app-sync deployment ls <appName> --displayKeys.
💁♂️ All new apps automatically come with two deployments (
Production) so that you can begin distributing updates to multiple channels. If you need more channels/deployments, simply run:
nativescript-app-sync deployment add <appName> <deploymentName>.
💁♂️ Want to rename your app? At any time, use the command:
nativescript-app-sync app rename <oldName> <newName>
💁♂️ Want to delete an app? At any time, use the command:
nativescript-app-sync app remove <appName>- this means any apps that have been configured to use it will obviously stop receiving updates.
List your registered apps
nativescript-app-sync app ls
Add this plugin to your app
tns plugin add nativescript-app-sync
⚠️ If you're restricting access to the internet from within your app, make sure you whitelist our AppSync server (
https://appsync-server.nativescript.org) and File server (
Checking for updates
With the AppSync plugin installed and configured, the only thing left is to add the necessary code to your app to control when it checks for updates.
If an update is available, it will be silently downloaded, and installed.
Then based on the provided
InstallMode the plugin either waits until the next cold start (
warm restart (
InstallMode.ON_NEXT_RESUME), or a positive response to a user prompt (
Note that Apple doesn't want you to prompt the user to restart your app, so use
InstallMode.IMMEDIATE on iOS only for Enterprise-distributed apps (or when testing your app through TestFlight for instance).
💁♂️ Check out the demo for a solid example.
// import the main plugin classes;// and at some point in your app:AppSync.sync;
There's a few things you can configure - this TypeScript example has all the possible options:
var AppSync = AppSync;var InstallMode = InstallMode;var SyncStatus = SyncStatus;var platform = ;AppSync;
When should this check run?
It's recommended to check for updates more than once in a cold boot cycle,
so it may be easiest to tie this check to the
resume event (which usually also runs on app startup):
;;// add this in some central place that's executed once in a lifecycleapplication.onapplication.resumeEvent,;
var application = ;application;
Releasing an update
Once your app has been configured and distributed to your users, and you've made some code and/or asset changes, it's time to instantly unleash those changes onto your users!
⚠️ Make sure to create a release build first, so use the same command that you'd use for app store distribution, just don't send it to the AppStore. You can even Webpack and Uglify your app, it's all transparent to this plugin.
💁♂️ When releasing updates to AppSync, you do not need to bump your app's version since you aren't modifying the app store version at all. AppSync will automatically generate a "label" for each release you make (e.g.
v3) in order to help identify it within your release history.
The easiest way to do this is to use the
release command in our AppSync CLI. Its (most relevant) options are:
|deploymentName||d||"Staging"||Deploy to either "Staging" or "Production".|
|description||des||not set||Description of the changes made to the app with this release.|
||Semver expression that specifies the binary app version(s) this release is targeting (e.g. 1.1.0, ~1.2.3). The default is the exact version in
|mandatory||m||not set||This specifies whether or not the update should be considered "urgent" (e.g. it includes a critical security fix). This attribute is simply round tripped to the client, who can then decide if and how they would like to enforce it. If this flag is not set, the update is considered "not urgent" so you may choose to wait for the next cold boot of the app. It does not mean users get to 'opt out' from an update; all AppSync updates will eventually be installed on the client.|
Have a few examples for both platforms:
nativescript-app-sync release <c-ios-appname> ios # deploy to Stagingnativescript-app-sync release <AppSync-ios-appname> ios --d Production # deploy to Production (default: Staging)nativescript-app-sync release <AppSync-ios-appname> ios --targetBinaryVersion ~1.0.0 # release to users running any 1.x version (default: the exact version in Info.plist)nativescript-app-sync release <AppSync-ios-appname> ios --mandatory --description "My mandatory iOS version" # a release for iOS that needs to be applied ASAP.
nativescript-app-sync release <AppSync-android-appname> android # deploy to Stagingnativescript-app-sync release <AppSync-android-appname> android --d Production # deploy to Production (default: Staging)nativescript-app-sync release <AppSync-android-appname> android --targetBinaryVersion ~1.0.0 # release to users running any 1.x version (default: the exact version in AndroidManifest.xml)
Click here to learn more about the --targetBinaryVersion paramThe `targetBinaryVersion` specifies the store/binary version of the application you are releasing the update for, so that only users running that version will receive the update, while users running an older and/or newer version of the app binary will not. This is useful for the following reasons:
If a user is running an older binary version, it's possible that there are breaking changes in the AppSync update that wouldn't be compatible with what they're running.
If a user is running a newer binary version, then it's presumed that what they are running is newer (and potentially incompatible) with the AppSync update.
If you ever want an update to target multiple versions of the app store binary, we also allow you to specify the parameter as a semver range expression. That way, any client device running a version of the binary that satisfies the range expression (i.e.
semver.satisfies(version, range) returns
true) will get the update. Examples of valid semver range expressions are as follows:
|Range Expression||Who gets the update|
||Only devices running the specific binary app store version
||Any device configured to consume updates from your AppSync app|
||Devices running major version 1, minor version 2 and any patch version of your app|
||Devices running any binary version between
||Devices running any binary version between
*NOTE: If your semver expression starts with a special shell character or operator such as
^, or **
, the command may not execute correctly if you do not wrap the value in quotes as the shell will not supply the right values to our CLI process. Therefore, it is best to wrap your
targetBinaryVersion parameter in double quotes when calling the
release command, e.g.
app-sync release MyApp-iOS updateContents ">1.2.3".
NOTE: As defined in the semver spec, ranges only work for non pre-release versions: https://github.com/npm/node-semver#prerelease-tags. If you want to update a version with pre-release tags, then you need to write the exact version you want to update (
1.2.3-beta for example).
The following table outlines the version value that AppSync expects your update's semver range to satisfy for each respective app type:
|Platform||Source of app store version|
NOTE: If the app store version in the metadata files are missing a patch version, e.g.
2.0, it will be treated as having a patch version of
2.0 -> 2.0.0. The same is true for app store version equal to plain integer number,
1 will be treated as
1.0.0 in this case.
Gaining insight in past releases
Here are a few AppSync CLI commands you may find useful:
Which releases did I create and what are the install metrics?
Using a command like this will tell you how many apps have the update installed:
nativescript-app-sync deployment history <appsync-appname> Staging
Which produces something like this:
|Label||Release Time||App Version||Mandatory||Description||Install Metrics|
|v2||an hour ago||1.0.0||Yes||Mandatory iOS version!||Active: 11% (2 of 19)|
|v1||2 hours ago||1.0.0||No||Awesome iOS version!||Active: 26% (5 of 19)|
Give me the details of the current release!
This dumps the details of the most recent release for both the Staging and Production environments of your app:
nativescript-app-sync deployment ls <appsync-appname>
And if you want to dump your deployment keys as well, use:
nativescript-app-sync deployment ls <appsync-appname> --displayKeys
Which produces something like this:
|Name||Deployment Key||Update Metadata||Install Metrics|
|Production||r1DVaLfKjc0Y5d6BzqX4..||No updates released||No installs recorded|
|Staging||YTmVMy0GLCknVu3GVIyn..||Label: v5||Active: 11% (2 of 19)|
|App Version: 1.0.0||Total: 2|
|Release Time: an hour ago|
|Released By: firstname.lastname@example.org|
|Description: Mandatory iOS version!|
Clearing the release history
This won't roll back any releases, but it cleans up the history metadata (of the
Staging app, in this case):
nativescript-app-sync deployment clear <appsync-appname> Staging
Testing AppSync packages during development
You may want to play with AppSync before using it in production (smart move!).
Perform these steps once you've pushed an update and added the
sync command to your app:
$ tns run <platform>. On an iOS device add the
--releaseflag so LiveSync doesn't interfere.
- kill and restart the app after the update is installed
Running the demo app
You may also play with AppSync by using its demo app. Here are the steps you need to perform in order to observe an app update:
- register with the service (
nativescript-app-sync register) and add the demo app to your account (
nativescript-app-sync app add <appname> <platform> nativescript)
- once the app is registered you will see its deployment keys in the console, use them to update the ones in the demo
- go to src and run
npm run preparedemo- this will build the plugin and add a reference to the demo app
- prepare an app that will be used as an "update version" (for example, uncomment one of the APPSYNC labels and comment the APPSTORE label), then run
tns build <platform>
- release the update (
nativescript-app-sync release <appname> <platform>)
- you can ensure it appears in the list with updates (
nativescript-app-sync deployment history <appname> Staging)
- prepare an app that will be used as an "official release version" (for example, comment the APPSYNC label and uncomment the APPSTORE label), then run
tns run <platform>
- when the app is deployed on the device, you should see the "official release version" along with information about an installed update
- close the app (and remove it from device's recent apps to ensure its next start will be a cold start) and run it again - you should now see the "update version" of the app
Patching Update Metadata
After releasing an update, there may be scenarios where you need to modify one or more of the metadata attributes associated with it (e.g. you forgot to mark a critical bug fix as mandatory.
Read all about patching metadata by clicking here.
You can update metadata by running the following command:
nativescript-app-sync patch <appName> <deploymentName>[--label <releaseLabel>][--mandatory <isMandatory>][--description <description>][--targetBinaryVersion <targetBinaryVersion>]
⚠️ This command doesn't allow modifying the actual update contents of a release. If you need to respond to a release that has been identified as being broken, you should use the rollback command to immediately roll it back, and then if necessary, release a new update with the approrpriate fix when it is available.
Aside from the
deploymentName, all parameters are optional, and therefore, you can use this command to update just a single attribute or all of them at once.
patch command without specifying any attribute flag will result in a no-op.
# Mark the latest production release as mandatorynativescript-app-sync patch MyAppiOS Production -m# Add a "mina and max binary version" to an existing releasenativescript-app-sync patch MyAppiOS Staging -t "1.0.0 - 1.0.5"
Read this if you want to easily promote releases from Staging to Production
Once you've tested an update against a specific deployment (e.g.
and you want to promote it (e.g. dev->staging, staging->production),
you can simply use the following command to copy the release from one deployment to another:
nativescript-app-sync promote <appName> <sourceDeploymentName> <destDeploymentName>[--description <description>][--label <label>][--mandatory][--targetBinaryVersion <targetBinaryVersion]# examplenativescript-app-sync promote AppSyncDemoIOS Staging Production --description 'Promoted from Staging to Production'
promote command will create a new release for the destination deployment, which includes the exact code and metadata (description, mandatory and target binary version) from the latest release of the source deployment.
While you could use the
release command to "manually" migrate an update from one environment to another, the
promote command has the following benefits:
It's quicker, since you don't need to reassemble the release assets you want to publish or remember the description/app store version that are associated with the source deployment's release.
It's less error-prone, since the promote operation ensures that the exact thing that you already tested in the source deployment (e.g.
Staging) will become active in the destination deployment (e.g.
💁♂️ Unless you need to make changes to your code, the recommended workflow is taking advantage of the automatically created
Productionenvironments, and do all releases directly to
Staging, and then perform a
Productionafter performing the appropriate testing.
Rolling Back Updates
Read this if you want to learn all about rollbacks
A deployment's release history is immutable, so you cannot delete or remove individual updates once they have been released without deleting all of the deployment's release history.
However, if you release an update that is broken or contains unintended features,
it is easy to roll it back using the
nativescript-app-sync rollback <appName> <deploymentName>#examplenativescript-app-sync rollback MyAppiOS Production
This has the effect of creating a new release for the deployment that includes the exact same code and metadata as the version prior to the latest one. For example, imagine that you released the following updates to your app:
|v2||Added new feature||No|
If you ran the
rollback command on that deployment, a new release (
v4) would be created that included the contents of the
|v2||Added new feature||No|
|v4 (Rollback from v3 to v2)||Added new feature||No|
End-users that had already acquired
v3 would now be "moved back" to
v2 when the app performs an update check.
Additionally, any users that were still running
v2, and therefore, had never acquired
v3, wouldn't receive an update since they are already running the latest release
(this is why our update check uses the package hash in addition to the release label).
If you would like to rollback a deployment to a release other than the previous (e.g.
v2), you can specify the optional
nativescript-app-sync rollback MyAppiOS Production --targetRelease v34
⚠️ This rolls back the release to the previous AppSync version, NOT the AppStore version (if there was one in between).
💁♂️ The release produced by a rollback will be annotated in the output of the
deployment historycommand to help identify them more easily.
Working on one app with multiple developers? Click here!
If you will be working with other developers on the same AppSync app, you can add them as collaborators using the following command:
nativescript-app-sync collaborator add <appName> <collaboratorEmail>
NOTE: This expects the developer to have already registered with AppSync using the specified e-mail address, so ensure that they have done that before attempting to share the app with them.
Once added, all collaborators will immediately have the following permissions with regards to the newly shared app:
- View the app, its collaborators, deployments and release history.
- Release updates to any of the app's deployments.
- Rollback any of the app's deployments
Inversely, that means that an app collaborator cannot do any of the following:
- Rename or delete the app
- Create, rename or delete new deployments within the app
- Clear a deployment's release history
- Add or remove collaborators from the app (although a developer can remove themself as a collaborator from an app that was shared with them).
Over time, if someone is no longer working on an app with you, you can remove them as a collaborator using the following command:
nativescript-app-sync collaborator rm <appName> <collaboratorEmail>
If at any time you want to list all collaborators that have been added to an app, you can simply run the following command:
nativescript-app-sync collaborator ls <appName>
Using AppSync behind a proxy
Click here to read all about Proxy SupportBy default, the `login` command will automatically look for a system-wide proxy, specified via an `HTTPS_PROXY` or `HTTP_PROXY` environment variable, and use that to connect to the server. If you'd like to disable this behavior, and have the CLI establish a direct connection, simply specify the `--noProxy` parameter when logging in:
nativescript-app-sync login --noProxy
I'd you like to explicitly specify a proxy server that the CLI should use, without relying on system-wide settings,
you can instead pass the
--proxy parameter when logging in:
nativescript-app-sync login --proxy https://foo.com:3454
Once you've logged in, any inferred and/or specified proxy settings are persisted along with your user session. This allows you to continue using the CLI without needing to re-authenticate or re-specify your preferred proxy. If at any time you want to start or stop using a proxy, simply logout, and then log back in with the newly desired settings.
- Got build errors related to the nativescript-zip plugin? Please check out the solution in this issue.