active_reach_sdk

Android build fix — 0.8.0 failed to compile against android-sdk 1.7.0.

• Dropped the enableAdaptiveBatching init param: it was passed to the native AegisConfig, which has no such field (the engine has no adaptive-batching feature), so every Android consumer build failed at compileDebugKotlin.
• Consumer note: the native engine requires minSdk 26 — apps using this plugin must set minSdkVersion/minSdk to 26 or higher.

Build fix for external consumers — 0.7.0 could not build on Android.

• Android: the plugin now depends on the published ai.active-reach:android-sdk:1.7.0 Maven Central artifact. 0.7.0 referenced an internal monorepo Gradle path (project(':libs:mobile-sdk:android-sdk')) that broke every external Android build. Also declares an explicit namespace so it builds under AGP 8/9.
• iOS: the CocoaPods dependency now requires ActiveReachSDK ~> 1.7 (was ~> 1.6), matching the current native iOS SDK.

No Dart API changes.

First public release on pub.dev. Renamed from internal aegis_flutter to customer-facing active_reach_sdk (the internal Kotlin / Swift plugin classes retain the Aegis prefix per the brand canon — internal-only, never user-visible).

Features at first publish

• Events: track / screen / page / identify / alias / group / reset
• E-commerce: 19-method EcommerceTracker with canonical event names
• In-app: 5 preload-first renderers (modal, sticky bar, coach mark, spinner, quiz/rating) via SSE-driven prefetch
• Push: AegisPush lifecycle hooks against canonical /v1/push/engagement
• Consent: ConsentManager with 4 canonical categories
• Governance: TraitGovernor + NameGovernor (Bloom + Murmur3) mirroring the backend ingestion chokepoint
• Meta Pixel companion: MetaPixelCompanion for CAPI dedup (lastEventId exposed)
• Plugin system: PluginRegistry extension surface

Notes

• Targets feature-parity with @active-reach/[email protected] (web SDK is the parity reference; mobile SDKs catch up to web)
• http pinned to ^0.13.6 (not 1.x) because eventsource ^0.4.0 still requires it. Bump both together when eventsource ships an http 1.x compatible release.