react-native-code-push 1.9.0-beta

v1.9.0-beta

on Node.js NPM

This release introduces a couple of highly-requested features, as well as some key bug fixes. It is now available on NPM and can be updated immediately by running npm i --save react-native-code-push@latest.

New Features

1. Added client-side support for the new release rollout feature in the CLI This version of the React Native SDK is required in order to begin taking advantage of this new capability, so make sure to upgrade your apps before attempting to release updates with a rollout percentage. More details

   code-push release-react MyApp ios --rollout 25%

2. Added support for throttling resume-based installs We've seen a lot of developers want to use the resume-based install strategy, in order to get their updates in front of their end users sooner. However, forcing a restart on the next resume might be too obtrusive if the user switched away from the app for only a few seconds (e.g. to respond to a text). In order to help get updates in front of users sooner, while still respecting their workflow, the sync method now accepts a new option called minimumBackgroundDuration that specifies the number of seconds that the app needs to have been in the background before forcing the install. More details

   // If the app was in the background for 10 minutes, we assume that it is "safe" to restart to install the update
   codePush.sync({ installMode: codePush.InstallMode.ON_NEXT_RESUME, minimumBackgroundDuration: 10 * 60 });

Bug Fixes (General)

1. When an update is downloaded from the CodePush server, the plugin now looks for the JS bundle file using the exact same file name that was specified as being contained in the binary (via either [CodePush bundleURL] or CodePush.getBundleURL), as opposed to looking for the first file with a .jsbundle, .bundle or .js extension. This makes the update E2E more reliable, and prevents issues for apps that use local <WebView> hosted content.

Bug Fixes (iOS)

1. The contents of the app binary are now successfully hashed for apps that aren't using React Native assets
2. A custom error message is displayed when using [CodePush bundleURL] in your AppDelegate.m file, and deploying a debug build to the iOS Simulator. React Native doesn't generate a JS bundle in the binary in this circumstance, and it has confused many CodePush users. To help alleviate the confusion, we now explain the issue as well as a few possible workarounds.

Bug Fixes (Android)

1. Cleaned up a bunch of lint warnings that didn't impact behavior, but may have been noisy for devs integrating CodePush into a native Android app
2. Fixed an interop bug for apps that are using CodePush along with the Fabric SDK