WarpLink

SDK Changelog

What changed in WarpLink SDK 1.1.0 for iOS, Android, and React Native, and how to upgrade from an earlier version on each platform.

The current release across all three SDKs is 1.1.0, published 2026-09-15. This page covers what changed at a high level and how to upgrade. For the full per-line history, see each SDK's own CHANGELOG.md in its repository.

What Changed in 1.1.0

All three SDKs shipped the same set of changes:

  • Opt-out configuration. A single configure({ apiKey, onLink }) call now wires up cold-start deep links, warm-start deep links, and the deferred deep link check automatically. Each piece can still be turned off individually if you want to drive it yourself.
  • Custom link domains. The SDKs fetch your organization's verified custom domains and resolve links on them, instead of recognizing only aplnk.to. Declare domains locally with the linkDomains option (or the no-code manifest/plist equivalent) so a link resolves correctly on the very first launch, before the server response arrives.
  • Shorter deferred match window. The default lifetime of a deferred deep link payload dropped from 72 hours to 6, with a 24-hour ceiling. This affects the probabilistic (fingerprint) match tier only; deterministic matches (install referrer, device ID) are unaffected.
  • In-app opens now count as recorded clicks. A verified Universal Link or App Link that opens your app directly previously produced no click record. It now appears in analytics alongside browser redirects, and counts toward click deduplication the same way. This is a server-side change and applies to older SDK versions too.

Platform-Specific Changes

  • iOS: customParams changed type from [String: Any] to [String: JSONValue]. This is source-breaking if your code casts values out of customParams directly; use the typed accessors instead (for example, customParams["id"]?.stringValue).
  • Android and React Native: no source-breaking changes in this release.

Upgrading

Update your Swift Package Manager dependency to 1.1.0:

dependencies: [
    .package(url: "https://github.com/WarpLinkApp/warplink-ios-sdk", from: "1.1.0")
]

If any code reads customParams with a cast such as customParams["x"] as? String, switch to the typed accessor: customParams["x"]?.stringValue. Everything else is additive; no other code changes are required to upgrade.

Update your Gradle dependency to 1.1.0:

dependencies {
  implementation("app.warplink:sdk:1.1.0")
}

No source changes are required. The release is additive and backward compatible.

Update the npm package to 1.1.0:

npm install @warplink/react-native@1.1.0

No source changes are required. The release is additive and backward compatible.

  • SDK Overview: platform support and design principles across all three SDKs
  • Quickstart: install and configure a WarpLink SDK from scratch
  • Deferred deep links: how the match window and confidence tiers work

React Native API Reference

The complete TypeScript API reference for the WarpLink React Native SDK: initialization, deep link events, and attribution.

Migration

Migrate from Firebase Dynamic Links to WarpLink: link mapping, SDK setup, and attribution verification.

On this page

What Changed in 1.1.0Platform-Specific ChangesUpgradingRelated