> ## Documentation Index > Fetch the complete documentation index at: https://docs.appstack.tech/llms.txt > Use this file to discover all available pages before exploring further. # Flutter SDK changelog > Every release of the Appstack Flutter SDK, newest first. Releases of the `appstack_plugin` pub.dev package, newest first. Always integrate against the latest stable release — [`appstack-cli review`](/tooling/cli) will tell you what you are on. Install, configure, and send your first events. **Changed** * **Updated the Appstack iOS SDK to 4.6.0** * **Updated the Appstack Android SDK to 1.8.0** * **Custom `sendEvent()` parameters are encrypted on the device before being sent.** Parameter keys not in the backend's plaintext allowlist are sealed with RFC 9180 HPKE. The allowlist is served in remote config; no app or `configure()` change is required, and with no config block both SDKs send plaintext as before. `transaction_details`, deeplink user data, identifiers and other top-level event fields are not encrypted, and revenue is extracted before encryption, so revenue reporting is unchanged. A value that cannot be sealed is omitted and the event still sends. Requires iOS 17+; on iOS 15–16 values are encrypted server-side as before. Applies at Android's API 21 floor. No new dependency on either platform; the Android AAR grows \~36 KB. **Fixed** All three are iOS SDK 4.6.0 fixes; Android is unchanged. * **A `null` in `sendEvent()`'s `parameters` no longer drops the event on iOS.** Nulls are omitted from the payload; nulls inside lists are kept. This matches Android's existing behaviour. * **`sendEvent()` no longer crashes on iOS when a parameter value cannot be JSON-serialized.** The key is dropped and logged natively; the event sends with the rest. From Dart this covers `double.nan`, `double.infinity` and typed-data lists (`Uint8List`, `Int32List`, `Int64List`, `Float64List`). `DateTime`, `Uri`, `Set` and arbitrary objects are unaffected — they throw `ArgumentError` at the platform channel and never reach the SDK. * **A `null` in the attribution match response no longer discards the whole response on iOS.** One null query parameter could previously cost an install its attribution data. No Dart API changed. `sendEvent()`'s doc comment now describes null handling, the parameter value types that cross the platform channel, and the encryption. [Release notes on GitHub](https://github.com/appstack-tech/appstack-flutter-sdk/releases/tag/2.7.0) **Added** * `AppstackPlugin.setCustomerUserId(customerUserId)` — sets or clears the customer user ID after `configure()`, bridging the native iOS/Android setter of the same name. Use it when a login reveals the ID; calling `configure()` a second time does not work, as a repeat `configure()` is a no-op and ignores its `customerUserId`. Clear it on logout so the previous user's ID stops being attached to later events. Passing `null` (or a blank string) clears the stored ID — unlike `configure()`, which treats a blank value as "not provided" because it never clears. Safe to call at any time; last write wins. **Changed** * **Updated the Appstack iOS SDK to 4.5.0** — on iOS, `getAttributionParams()` no longer comes back empty: the map now always carries an `appstack_match_status` key reporting the attribution outcome (`matched`, `matched_no_params`, `organic`, `skipped`, `failed` or `not_configured`). Only `failed` is worth re-reading later; the rest are settled answers. The Dart signature is unchanged — the result is still nullable, so existing null checks keep working — but code that read an empty result as "not attributed" should switch to the status key. Treat the key as iOS-only for now: Android 1.7.0 does not add it, so an empty map still means "nothing yet" there. Also fixed on iOS: a `setCustomerUserId()` call made immediately after `configure()` is no longer overwritten by the `customerUserId` passed to `configure()`, and a blank customer user ID is treated as absent rather than sent as an empty string. * **Updated the Appstack Android SDK to 1.7.0** — adds the native `setCustomerUserId` setter that `AppstackPlugin.setCustomerUserId()` bridges on Android. No new permission is required. [Release notes on GitHub](https://github.com/appstack-tech/appstack-flutter-sdk/releases/tag/2.6.0) **Changed** * **Updated the Appstack iOS SDK to 4.4.1** — attribution matching now includes additional network context to improve match diagnostics. * **Updated the Appstack Android SDK to 1.6.0** — attribution matching now includes additional device and network context to improve match accuracy, and the Play install referrer is now resolved before the match request so attribution can be determined deterministically. No new permission is required. * **`EventType.install` is no longer sent when passed to `sendEvent()`** — both native SDKs already track the install automatically, so sending it by hand previously double-counted installs. Such calls are now logged and discarded natively; the Dart call still succeeds. **Fixed** * **Android: a remotely disabled app no longer fires the attribution match request** — previously `enabled=false` suppressed only the event POSTs, and a fresh install still called `/attribution/match`. A disabled app now makes no attribution network calls at all. [Release notes on GitHub](https://github.com/appstack-tech/appstack-flutter-sdk/releases/tag/2.5.0) **Changed** * **Updated the Appstack iOS SDK to 4.4.0** * **Updated the Appstack Android SDK to 1.5.0** * Raised the minimum supported iOS version to **15.0** (required by iOS SDK 4.4.0). This applies to both integration paths — the Swift Package Manager package (`Package.swift`) and the CocoaPods podspec. [Release notes on GitHub](https://github.com/appstack-tech/appstack-flutter-sdk/releases/tag/2.4.0)