Gathering detailed insights and metrics for taro-rn-update
Gathering detailed insights and metrics for taro-rn-update
Gathering detailed insights and metrics for taro-rn-update
Gathering detailed insights and metrics for taro-rn-update
Update apk from non-play store servers, and update ios from app store in React Native.
npm install taro-rn-update
Typescript
Module System
Node Version
NPM Version
v5.0.0 - AndroidX migration, drop Android 4 support, semver for version compare
Updated on Jun 12, 2021
v4.5.1 - Xcode 12 build compatibility
Updated on Sep 17, 2020
v4.5.0 - apkOptions, similar to apkVersionOptions - custom headers for APK fetch
Updated on Jun 27, 2020
v4.4.0 - custom HTTP options, better App Store URL, 'whats new' info
Updated on Jun 25, 2020
v4.3.2 - change internal variable name for unknown babel compatability issue
Updated on May 08, 2020
v4.3.1 - allow appCompatVersion as gradle var vs supportLibVersion
Updated on Mar 05, 2020
Java (39.25%)
JavaScript (26.74%)
C++ (11.52%)
Objective-C++ (7.02%)
Objective-C (6.05%)
Shell (4.87%)
Ruby (3.16%)
Starlark (0.95%)
CMake (0.43%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
203 Stars
178 Commits
57 Forks
2 Watchers
4 Branches
10 Contributors
Updated on Jun 11, 2025
Latest Version
5.0.2
Package Id
taro-rn-update@5.0.2
Unpacked Size
40.72 kB
Size
12.67 kB
File Count
16
NPM Version
10.5.0
Node Version
21.7.1
Published on
Sep 18, 2024
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
2
3
Easily check for new APKs and install them in React Native.
1npm install rn-update-apk --save
FileProviders: Android API24+ requires the use of a FileProvider to share "content" (like downloaded APKs) with other applications (like the system installer, to install the APK update). So you must add a FileProvider entry to your AndroidManifest.xml, and it will reference a "filepaths" XML file. Both are demonstrated in the example as linked here.
Permissions For Android 25+ you need to add REQUEST_INSTALL_PACKAGES to your AndroidManifest.xml
Please install and run the example to see how it works before opening issues. Then adapt it into your own app. Getting the versions right is tricky and setting up FileProviders is very easy to do incorrectly, especially if using another module that defines one (like rn-fetch-blob)
Please see the example App.js as it is very full featured and
has very thorough documentation about what each feature is for. You just need to check out the module from github, cd example && npm install && npm start
then react-native run-android
in another terminal with an emulator up to see everything in action.
See the Changelog on github
This application has been tested on API21+. Older versions of this library also supported API16-20 with HTTPS updates working via a patch to SSL services achieved via Google Play Services. This has been removed now that react-native only supports API21+. Use older versions if you support API16-20.
Note that you can host tests on dropbox.com using their "shared links", but if you do so will need to put '?raw=1' at the end of the link they give you so you get the raw file contents instead of a non-JSON XML document
1// version.json example 2// Note you will need to verify SSL works for Android <5 as it has SSL Protocol bugs 3// If it doesn't then you may be able to use Google Play Services to patch the SSL Provider, or just serve your updates over HTTP for Android <5 4// https://stackoverflow.com/a/36892715 5{ 6 "versionName":"1.0.0", 7 "apkUrl":"https://github.com/NewApp.apk", 8 "forceUpdate": false, 9 "whatsNew": "<< what changes the app update will bring >>" 10}
No vulnerabilities found.
Reason
license file detected
Details
Reason
binaries present in source code
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 1/14 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
18 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More