Skip to content

Releases: mikehardy/react-native-update-apk

v4.0.2

20 Jul 04:25
b07ee7b
Compare
Choose a tag to compare

This release adds the required android/build.gradle changes so you can use the library successfully in a react-native 0.60 project

The example has also been updated to react-native 0.60 - if you want to continue to see how to use it in react-native 0.59, switch to the tag v4.0.1 and browse the example code that way

The changes are backwards compatible and all prior support react-native versions should continue to work.

v3.2.4 documenation updates only

16 Mar 21:55
24767ba
Compare
Choose a tag to compare

3.2.4

  • Enhanced the README, changed TODO to match current state of the project

v3.2.3 Looks production ready - more example doc updates

16 Mar 21:11
0ec3338
Compare
Choose a tag to compare

This is the release where I consider the module tested (API16 to API28, with and without Google Play Services) and it appears to work well when it can and provide good troubleshooting information when it cannot work.

I am integrating this version into a commercial app and it should be ready to go although I'm sure there will be fixes here and there.

I will eventually change the API to have more Promises, and will hopefully add the ability to do pause/resume downloads built-in as well as other things from the TODO list, but in the current condition you should be able to use this module to keep your app updated, and any updates will follow semver and should behave as expected for major/minor/patch.

For bonus points, I will mention that you can store the version.json and an APK in dropbox.com using one of their public "shared links" if you just add '?raw=1' to the links for the JSON fetch inside your app, and to the APK inside the JSON, and it can drive your APK upgrading. Good luck!

3.2.3

  • Continuing to add FileProvider example notes, better exception handling
    This is easily the part that can trip people up the most

v3.2.2 example documentation, FileProvider demo improvements

16 Mar 21:05
20bc84e
Compare
Choose a tag to compare

3.2.2

  • Added extensive notes to the example about purpose of each demonstrated feature
  • Altered example FileProvider name to be consistent with rn-share-blob to help users

v3.2.1 use file:// style for Android < API24

15 Mar 21:53
efb9645
Compare
Choose a tag to compare

3.2.1

  • Fix issue introduced in v3.0.0 with installing package on old devices
    This works now in my testing from API16 to API28, assuming API16-20 have Google Play
    Services if you want to download over SSL
  • Switch to non-deprecated Play Services availability APIs

v3.2.0 Patch SSL for Android 4.x via Play Services if available

15 Mar 21:52
16cd478
Compare
Choose a tag to compare

3.2.0

  • Attempt to use Play Services to patch SSL for Android <5
  • Example updated to show how to handle SSL download errors

v3.1.1 example perfection, signing info, download progress

15 Mar 02:19
a11775b
Compare
Choose a tag to compare

The example is now perfect, and shows the new information available about the signing certificate for the current and downloaded app. Additionally the example demonstrates download progress as well

v3.0.1 - more package info, new test target

14 Mar 04:15
002c39b
Compare
Choose a tag to compare

Previous release covered API24+ with FileProviders

This release provides much more package information prior to upgrade (version info, install/update time info, etc)

With the info about install / update time this serves as a good test target since it can show you when updates happened (thus confirming that an update worked)

Note that the APK here is named "3.0.1" but I actually update it when necessary to serve as a stable download target for master

v2.0.1 - the "it works" edition, with example

12 Mar 04:06
d30a1b4
Compare
Choose a tag to compare

I'm currently testing this fully integrated into an app that will be in production shortly, for Android everything appears to work fine

Also the example APK in this release is the target for the example app. The test-version.json declares an available version of "999" (guaranteed to always prompt for an update) but specifies the 2.0.1 version of the example (so you can re-check for updates any time)