Versions & Changelog

The current LinkTrail SDK versions, the minimum OS each supports, which native SDKs the wrappers pin, the breaking changes, and where each changelog lives.

The versions the docs are written against — each one is what its registry serves today: CocoaPods and the GitHub release for iOS, Maven Central for Android, npm for React Native and pub.dev for Flutter. Every install line in these docs pins the version below.

SDKPackageCurrentMinimumChangelog
iOSLinkTrailSDK (Swift Package Manager, CocoaPods)0.1.0iOS 15, Xcode 15 / Swift 5.9Releases
Androidio.linktrail:sdk (Maven Central)0.1.0minSdk 26Releases
React Nativelinktrail-react-native (npm)0.1.0React Native 0.76+ (New Architecture), iOS 15.1, minSdk 26CHANGELOG
Flutterlinktrail_flutter (pub.dev)0.1.0iOS 15, minSdk 26CHANGELOG

What the wrappers run on

React Native and Flutter call the native SDKs, so their behaviour — consent, the click token, the log lines — is the native SDKs'. Each pins a version range:

WrapperiOS SDKAndroid SDK
React Native 0.1.0~> 0.1.0 in its podspecio.linktrail:sdk:0.1.0
Flutter 0.1.0~> 0.1.0 in its podspecio.linktrail:sdk:0.1.0

A project with an older Podfile.lock can still be on an earlier iOS SDK. Run pod update LinkTrailSDK in ios/ to move it to the current one.

Upgrading to 0.1.0

All four SDKs moved to 0.1.0 together. It is a 0.x minor bump with breaking changes; the full checklist, with what to change on each platform, is on Upgrading to 0.1.0.

Breaking changes

SDKVersionWhat changedWhat to do
All four0.1.0handleDeepLink claims only https links on linktrail.io (or a subdomain) and on the hosts listed in linkDomains. Any other URL returns false (React Native: null) with no request and no onError; custom-scheme LinkTrail links are no longer handled.List every custom domain in linkDomains. Links on *.linktrail.io need no change.
All four0.1.0LinkTrailPasteButton's grantsConsent default now grants consent only if it is still undecided (it no longer overrides a denial). true always grants, false never touches consent. The React Native and Flutter buttons send the install themselves.Pass grantsConsent: true only for an explicit opt-in UI. Remove setConsent / trackInstallWithClickToken calls from the wrapper buttons' callbacks.
All four0.1.0With requireConsent: false, an explicit setConsent(false) now wins: one consent: false install with no device ID, custom events dropped.Nothing, unless you relied on a denied install still being counted.
All four0.1.0SDK state is device-only and no longer backed up: a restored or new phone counts as a new install. Non-retryable event failures (400, 401, 403, 404, 409, 422) are dropped, not queued. Log levels read WARNING (was WARN).Ask for consent again after a restore. Update log filters and alerts.
iOS0.0.12The install is held until your app records a consent decision. With the default requireConsent: true, an app that never calls setConsent sends nothing: no install, no attribution, no deferred link.Wire both answers of your consent prompt to setConsent, or pass requireConsent: false if consent is collected elsewhere.
Android0.0.5The install is held until a consent decision, instead of an unattributed install going out before the prompt is answered.The same: call setConsent(true) or setConsent(false) once your prompt resolves.
iOS0.0.10readClipboardOnInstall was removed and replaced by clickTokenSource, whose default .pasteButton reads the click token only when the user taps a paste control.Render LinkTrailPasteButton, or pass .automatic to keep reading the clipboard at install.

Each release's full notes are in the changelog links above. Upgrading across the consent change? Consent & privacy is the model all four SDKs now share.