Skip to main content

​
Overview

The Encore Flutter SDK is published as the public encore_flutter package on pub.dev. Because the plugin bundles the native iOS (EncoreKit CocoaPod) and Android (com.encorekit:encore AAR) SDKs, updating is a two-part flow: bump the Dart package, then refresh the native iOS pods so the updated EncoreKit binary is picked up.

​
Versioning policy

Encore follows Semantic Versioning: Use a caret constraint so patch and minor updates arrive through a routine flutter pub upgrade and a major version never lands without you opting in:
The plugin pins the native SDKs it was built against, so a plugin update is also a native update on both platforms. That is why a plugin 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 currently resolved version is recorded in pubspec.lock. The latest published version is listed on the package’s pub.dev page. You can also check from the command line:
This lists your current, upgradable, and latest resolvable versions for every dependency, including encore_flutter.

​
Update the package

1

Upgrade within your major version

This resolves the newest release your constraint allows, without editing pubspec.yaml.
2

Refresh the native iOS pods

The EncoreKit CocoaPod is pulled in transitively by the plugin. Run pod install with --repo-update so CocoaPods fetches the newest spec and installs the updated native binary:
Android requires no separate step: the updated com.encorekit:encore AAR is resolved automatically by Gradle on your next build.
3

Rebuild the app

Building fresh ensures both the Dart layer and the updated native SDKs are compiled in.

​
Verify the update

Confirm the resolved version in pubspec.lock matches the latest release in your major, or re-run:
If you encounter issues after updating, reach out to admin@encorekit.com.