unity_kit

Fixed

• MissingPluginException after the active UnityView is disposed (#4). When the platform view backing the active UnityView was destroyed (e.g. the screen was popped), the Dart side kept targeting the dead com.unity_kit/unity_view_N channel and the bridge stayed ready, so the next send/sendWhenReady crashed with MissingPluginException. Native (iOS + Android) now emits an onViewDisposed notification before tearing the channel down; the bridge resets readiness back to initializing, so sendWhenReady() queues messages until the next UnityView attaches and send() throws a typed EngineNotReadyException instead.
• Duplicate platform events after re-initialize(). Calling UnityBridgeImpl.initialize() again after unload() subscribed to the platform event stream a second time, duplicating every message/event. The previous subscription is now cancelled first.

Breaking

• Minimum SDK raised to Dart 3.4 / Flutter 3.22 (required by the modern dart:js_interop web implementation). Existing mobile API usage is unchanged.
• UnityBridge gained sendBinary, sendBinaryWhenReady, and performanceStream. Code that calls the bridge is unaffected; only code that directly implements UnityBridge (e.g. custom mocks) must add the three members. UnityBridgeImpl and the bundled mocks already do.

Added

• Binary protocol. UnityBinaryCodec compact wire format with UnityBridge.sendBinary() / sendBinaryWhenReady(), plus UnityBinaryWriter / UnityBinaryReader for hand-packed payloads. Mirrored on the Unity side by UnityKitBinaryCodec + FlutterBridge.ReceiveBinary.
• Performance monitoring. UnityBridge.performanceStream emitting UnityPerformanceStats (FPS, frame time, used memory), produced by the new UnityKitPerformanceMonitor MonoBehaviour.
• AR Foundation. UnityConfig.ar() factory and UnityArMode (none / passthrough / overlay), wired to native creation params and a dependency-free UnityKitArSession bridge on the Unity side.
• Attribute dispatch. [UnityKitMethod] attribute + MessageRouter.RegisterMethods(target, instance) to expose C# methods to Flutter by name via reflection.
• Game manager. UnityKitGameManager MonoBehaviour handling load/unload scene, target frame rate, and pause/resume from Flutter.
• Web (WebGL) support. UnityKitWeb plugin registering the com.unity_kit/unity_view platform view via HtmlElementView, bridging through the per-view method channel.
• Desktop scaffolding. macOS / Windows / Linux plugins register the method channel so the Dart bridge API is callable; embedded player view is WIP.
• Project validator. Editor menu Tools ▸ UnityKit ▸ Validate Project.
• UnityConfig.toCreationParams() as the single source of truth for the Dart → native config contract (now also carries sceneName and arMode).

Changed

• UnityView now renders an HtmlElementView on web.
• iOS and Android now read arMode / sceneName from the view creation params: UnityArMode.overlay enables transparent rendering automatically, and both values are forwarded to Unity as a __unitykit_init message that UnityKitGameManager consumes.

Added

• UnityConfig.embedded() factory for creating an embedded (non-fullscreen) Unity view configuration, mirroring the existing UnityConfig.fullscreen() factory. Optionally accepts transparentBackground.

Added

• UnityConfig.transparentBackground flag that renders the native Unity container non-opaque on iOS so Flutter widgets painted behind the platform view can show through. Requires the Unity scene camera's clear colour to use alpha 0.
• UnityConfig.fullscreen() factory now accepts transparentBackground.
• iOS UnityKitView recursively applies isOpaque = false and a clear background to the Unity root view hierarchy when the flag is enabled.

Changed

• UnityConfig.toString() now reports every field, including transparentBackground, so it stays in sync with == / hashCode.
• UnityView logs a warning via UnityKitLogger when transparentBackground is enabled on Android (iOS-only feature).

Changed

• Updated installation docs to ^1.0.3

Changed

• Android compileSdk: 34 → 35
• androidx.lifecycle: 2.7.0 → 2.8.7
• androidx.annotation: 1.7.1 → 1.9.1

Fixed

• iOS: Unity view re-navigation — detachUnityView() now checks superview === self before removing, preventing race conditions when a new container has already claimed the Unity view.
• iOS: Rendering restart — added restartRendering() to UnityPlayerManager that calls showUnityWindow() after view reattachment, ensuring AR subsystems (e.g. Vuforia) reinitialize properly.
• iOS: CocoaPods dangling symlink — podspec no longer uses File.symlink? which returns true for dangling symlinks, causing CocoaPods realpath to fail with ENOENT.
• Dart: Active view channel routing — all platform method calls now use _activeViewId instead of hardcoded 0, ensuring correct MethodChannel routing after Flutter navigation creates new platform views.
• Added registerViewChannel(int viewId) to UnityKitPlatform — automatically called when a new platform view is created on both Android (Hybrid Composition) and iOS (UiKitView).

Changed

• Stable release — API is now considered stable. Follows Semantic Versioning from this point.
• _RoutedUnityMessage now exposes logical gameObject, method, type, and data properties matching the actual target (e.g. FlutterAddressablesManager), while routing through FlutterBridge.ReceiveMessage at the native layer via nativeGameObject/nativeMethod.

Added

• UnityMessage.nativeGameObject and UnityMessage.nativeMethod getters for accessing the native UnitySendMessage target separately from the logical message properties.
• UnityAssetLoader.loadContentCatalogMessage — request Unity to load a remote content catalog by URL (Addressables).
• "Why Addressables?" section in README — explains how dynamic content delivery keeps app size ~100 MB instead of 500 MB+.

Fixed

• All 22 previously failing tests in streaming/ and loaders/ now pass — routed messages correctly expose target info through standard UnityMessage properties.