Routine updates

Overview

The Encore Android SDK ships on Maven Central. Updating is the standard Gradle dependency flow, with no token or authenticated repository required.

Versioning policy

Encore follows Semantic Versioning:

Version change	Example	What it means
Patch	`2.0.0` → `2.0.1`	Bug fixes only. Always safe to update.
Minor	`2.0.1` → `2.1.0`	New features, backward compatible. Safe to update.
Major	`1.4.x` → `2.0.0`	Breaking changes. Follow that version’s migration guide.

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:

dependencies {
    implementation("com.encorekit:encore:2.+")
}

Upgrading across a major version? See Updating to 2.x for the step-by-step migration guide.

Update the dependency

Bump the version in your build.gradle.kts (or version catalog), then sync:

./gradlew --refresh-dependencies build

If you pin an exact version (recommended for reproducible builds), change it explicitly:

implementation("com.encorekit:encore:2.0.0")

Verify the update

Check the resolved version in Android Studio’s External Libraries, or:

./gradlew :app:dependencies --configuration releaseRuntimeClasspath | grep encorekit

If you encounter issues after updating, reach out to admin@encorekit.com.

iOS

Android

Web

Bridges

Routine updates

Overview

Versioning policy

Update the dependency

Verify the update

​Overview

​Versioning policy

​Update the dependency

​Verify the update

Overview

Versioning policy

Update the dependency

Verify the update