Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/aravind3566/react-native-in-app-updates/llms.txt

Use this file to discover all available pages before exploring further.

Adding react-native-in-app-updates to your project takes less than two minutes. The package ships a Kotlin native module registered under the name InAppUpdates, and React Native 0.60+ auto-links it automatically during the next build — no manual react-native link step needed.
This library is Android-only. The package installs and imports safely in projects that also target iOS; on iOS, checkForUpdate returns a rejected promise with the message "This library is only available on Android." rather than crashing, so you can branch on platform or simply catch the error.

​
Install the package

Choose your package manager: 
npm install react-native-in-app-updates

​
Rebuild for native module linking

Because the library includes a native Kotlin module, you must rebuild your app after installation. Auto-linking handles the wiring on React Native 0.60 and above — no extra configuration is required.
1

Clean the previous build (recommended)

cd android && ./gradlew clean && cd ..
2

Run the app to trigger linking

npx react-native run-android
The build process picks up the new module automatically via React Native’s auto-linking resolver.
Do not test in Expo Go. Expo Go does not support custom native modules. If you are using Expo, you must use a development build (expo-dev-client) or eject to a bare workflow.

​
Google Play Core dependency

The library’s android/build.gradle declares the Play Core dependencies directly, so you do not need to add anything to your own Gradle files: 
implementation("com.google.android.play:app-update:2.1.0")
implementation("com.google.android.play:app-update-ktx:2.1.0")
These are pulled in transitively when you build the Android project. Your app’s build.gradle needs no modification.
If your project already declares a different version of com.google.android.play:app-update, Gradle’s dependency resolution will pick the higher of the two versions. Versions 2.x of the Play In-App Update library are stable and backwards-compatible.
After rebuilding, confirm the native module is accessible by importing and calling checkForUpdate. If the module is not linked correctly, you will see a descriptive error at runtime: 
The package 'react-native-in-app-updates' doesn't seem to be linked. Make sure:

- You rebuilt the app after installing the package
- You are not using Expo Go
A successful link produces no error on import. The quickest smoke-test is: 
import { checkForUpdate, UpdateFlow } from 'react-native-in-app-updates';

// On Android this triggers the Play Core flow; on iOS it rejects gracefully.
checkForUpdate(UpdateFlow.FLEXIBLE).catch(console.warn);
If you see Success: or No update available in your logs (or the graceful iOS rejection), the module is linked correctly and you are ready to proceed.

Build docs developers (and LLMs) love

Get started for freeTalk to us