Skip to main content

​
Overview

The Encore React Native SDK is published as the public @encorekit/react-native package on npm. The package includes native bridges for both iOS and Android, so updating is a two-part flow: bump the npm package, then refresh the native iOS pods so the updated iOS SDK is picked up. Android is resolved automatically on the next build.

​
Versioning policy

Encore follows Semantic Versioning: Keep your dependency pinned within a major version so patch and minor updates arrive through a routine sync and a major version never lands without you opting in:
The bridge pins the native SDKs it was built against, so a bridge update is also a native update on both platforms. That is why a bridge major tracks a native major.
Upgrading across a major version? See Updating to 2.x for the step-by-step migration guide.

​
Check the current and latest version

Your installed version is recorded in package.json and locked in your lockfile (package-lock.json or yarn.lock). The latest published version is listed on the package’s npm page. You can also check from the command line:
To see whether your project is behind:

​
Update the package

1

Update within your major version

Install the newest release your constraint allows:
2

Refresh the native iOS pods

Run pod install with --repo-update so CocoaPods fetches the newest spec and installs the updated native iOS dependency:
Android requires no separate step: React Native auto-links the updated native module, and Gradle resolves it automatically on your next build.
3

Rebuild both platforms

Build fresh so the updated JavaScript and native layers are compiled in:

​
Verify the update

Confirm the installed version matches the latest release in your major:
If you encounter issues after updating, reach out to admin@encorekit.com.