Releases: microsoft/react-native-code-push
v2.0.2-beta
Bug Fixes
- Fixed a couple of new compilation errors that occurred when building iOS app extensions (#783).
v2.0.1-beta
Breaking Changes
Due to platform changes, [email protected]
will only support [email protected]
and onwards. Users on [email protected]
and lower should consult our compatibility table to determine the latest react-native-code-push
version to install.
New Features
- This release adds support for React Native 0.43 (@sergey-akhalkov, @Silhouettes, @nihgwu)
Bug Fixes
v1.17.3-beta
This is a small bug fix release. Thank you to @ymusiychuk-lohika, @buptkang, @abodalevsky, @max-mironov, @sergey-akhalkov, @timscott and @legalosLOTR for your contributions since the last release!
Bug Fixes (Android)
- Fix build issues by reverting Android SDK Build Tools version to 23.0.1, the version specified in the React Native docs.
- Address Flow type checking error caused by CodePush hash file being named
CodePushHash.json
despite not containing JSON.
Bug Fixes (Windows)
- Fix an exception caused by the destination folder already existing when unzipping packages.
- Fix an exception thrown when the
ProcessorID
property cannot be determined.
Note that support for [email protected]
is coming, and will be introduced in v2.0.0-beta
!
v1.17.1-beta
New Feature
- Added React Native Windows dotNet46 support #684, thanks @abodalevsky and @rozele.
Bug Fixes
- (Android) Fixed the issue #650 that the timestamp returned in getBinaryResourcesModifiedTime() always returns 312796800000 (11/30/1979, 12:00:00 AM). Thanks @sergey-akhalkov.
- (Both iOS and Android) Fixed the issue #574 that AsyncStorage(get/set...) operation will be blocked while downloading the bundle. Thanks @sergey-akhalkov.
- (iOS) Fixed the issue #661 that react-native link bug when using firebase . Thanks @max-mironov.
Document Upgrade
Since the documentation becomes more complex, we decomposed the document to have a better user experience. Thanks @jeremistadler.
v1.17.0-beta
New Features
- This release adds support for React Native 0.40.0 (@christopherdro, @sergey-akhalkov, @vladimir-kotikov, @buptkang)
- Significantly reduced final size of app once CodePush is integrated (@vladimir-kotikov)
Bug Fixes
- Support build for 'Android Plugin for Gradle' versions lower than 1.3.0 (@sergey-akhalkov)
- The linking/installation process is now significantly more robust (@matrosov-nikita) to conditions such as:
- No iOS or android directory
- The main application file is not named
MainApplication.java
- The
Info.plist
file is not in the same directory as theAppDelegate.m
file - The
.mm
extension is used instead of.m
- Single quotes are used in the react.gradle file
v1.16.1-beta
This release fixes a compilation error when integrating CodePush using CocoaPods into a Swift-based iOS app.
v1.16.0-beta
New Features
- This release adds support for React Native 0.36.0 (and 0.37.0). For details about issues with using prior versions of CodePush with RN 36/37, please see #582.
Bug Fixes
v1.15.1-beta
Thank you @piyushjo for verifying this release!
Bug Fixes
- Fix a comparison check on Android that could cause an issue in the bundle loading behavior on some devices. We highly recommend upgrading to this version if you were previously on
[email protected]
. (@Swordsman-Inaction) - Fix linking errors that may occur when the user has multiple
AppDelegate.m
files (@hilkeheremans) - Prevent the app's project name from possibly being overriden by CodePush's settings.gradle
v1.15.0-beta
This release improves stability across a wide range of platforms and React Native versions.
New Features
- Adds support for both React Native 0.34 and 0.35. Thanks so much for your patience!
- Updates will now be downloaded from a CDN to improve performance for users globally. To maintain backwards compatibility for those using a whitelist of approved URL endpoints, this will only apply from this release onwards.
- Allows the
node_modules
path to be overriden incodepush.gradle
. Thanks @geof90!
Bug Fixes (iOS)
- Uses
NativeEventEmitter
andRCTEventEmitter
instead of the deprecatedDeviceEventEmitter
. Thanks for kicking this off @Pho3nix! - Adds a class guard in
initialize
methods to allow for clean sub-classing, and fix a build warning about implicit type conversion. Thanks @daniel-beard!
Bug Fixes (Android)
- Fixes a crash that may happen when
CodePush.getUpdateMetadata()
is called when running against the binary version and an update is pending. Thanks @cmcewen! - Prevents a hash mismatch issue that may sometimes occur due to
.DS_Store
and__MACOSX
files generated on OS X (this was previously fixed on iOS only). - Removes unnecessary config from
AndroidManifest.xml
to fix manifest merging issues. Thanks @felipecsl!
Bug Fixes (Universal Windows Platform)
- Fixes an issue where rollbacks can occur erroneously when using
InstallMode.SILENT
. Thanks @rozele! - Fixes an issue where the app can hang when resuming while using
InstallMode.ON_NEXT_RESUME
. Thanks @rozele! - Fixes an issue where update check results were being cached for the lifetime of the app. Thanks for diagnosing this @rozele!
- Numerous style and code cleanliness improvements, including using best practices for
async
methods. Thanks @rozele!
v1.14.6-beta
New Features
- Adds support for setting a custom
ReactNativeHolder
viaCodePush.setReactInstanceHolder()
. This is useful if you're explicitly launching a React Native instance without an Activity (for example, from within a native push notification receiver). For these situations, CodePush must be told how to find your React Native instance in order to execute a forced restart whenever an update is installed. Thanks @igrayson for your contribution! - Exposes
isPendingUpdate
andisFailedHash
publicly on the iOS native API, however these are not documented methods, so they may run the risk being broken by future releases. Thanks @daniel-beard!
Bug Fixes
- For android users using React Native v0.32, during forced app restarts, due to changes in React Native internal APIs we would end up using the legacy logic that recreates the current activity, which does not result in the best experience. This is fixed in this release.
- Fixes a nil object insertion crash which occurs when a rollback is triggered while there is no current update present.
- Prevent crashes caused by NSError nil pointer dereferences throughout the iOS native API. Thanks @daniel-beard!