From 93bd4d6b4ab4baa3b1b104efaaaa6bc9914c6f96 Mon Sep 17 00:00:00 2001 From: Jonathan Carter Date: Wed, 30 Dec 2015 09:57:29 -0800 Subject: [PATCH] Rollback detail --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 37b847b..8be800c 100644 --- a/README.md +++ b/README.md @@ -25,6 +25,8 @@ A React Native app is composed of JavaScript files and any accompanying [images] The CodePush plugin helps get product improvements in front of your end users instantly, by keeping your JavaScript and images synchronized with updates you release to the CodePush 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 CodePush 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 to the "last known good". This way, you can rest assured that your new found release agility can't result in any users becoming getting by a bad update before you have a chance to [roll it back](http://microsoft.github.io/code-push/docs/cli.html#link-8) on the server. It's a win-win-win! + *Note: Any product changes which touch native code (e.g. modifying your `AppDelegate.m`/`MainActivity.java` file, adding a new plugin) cannot be distributed via CodePush, and therefore, must be updated via the appropriate store(s).* ## Supported React Native platforms