feat: MAUI integration hooks and refactor

[abelonogov-ld]

Summary

Refactors the Android Observability SDK architecture to align with the iOS/Swift and MAUI integration patterns, decoupling the Observability plugin from SessionReplay so each can function independently.

Architectural Changes

• Decoupled plugin dependency direction: SessionReplayService can depend on Observability, but Observability no longer depends on SessionReplay. Removed InstrumentationContributor, InstrumentationContributorManager, and the LDExtendedInstrumentation-based registration flow.
• Renamed for parity with Swift: ReplayInstrumentation → SessionReplayService, ReplayControl → SessionReplayServicing.
• Simplified log processing pipeline: Removed RoutingLogRecordProcessor and the per-instrumentation log routing mechanism from InstrumentationManager, since it was only used by session replay and no longer needed.
• SessionManager exposed via context: InstrumentationManager now captures the OTel SessionManager via a lightweight bridge AndroidInstrumentation and exposes it through ObservabilityClient → ObservabilityContext.sessionManager, matching the Swift pattern.

Session Replay Changes

• Plugin lifecycle: SessionReplay.register() directly creates SessionReplayService using LDObserve.context, wires it to LDReplay, and sets the hook delegate. SessionReplay.onPluginsReady() calls sessionReplayService.initialize() after SessionManager is available.
• Hook refactoring: SessionReplayHook no longer holds a reference to the SessionReplay plugin. Instead, it uses a @Volatile delegate of type SessionReplayServicing and extracts context keys from SDK types before delegating.
• afterIdentify moved to service layer: Context key extraction and LDContext building now happen in SessionReplayService.afterIdentify() and SessionReplayHook.afterIdentify() respectively, using a Map<String, String> interface for cross-platform compatibility.
• New SessionReplayHookProxy: JVM adapter for the C#/MAUI bridge that accepts simple JVM types and delegates to SessionReplayServicing.
• Wake-up events: Added RRWebEventGenerator.generateWakeUpEvents() and SessionReplayExporter.wakeUpEvents() to re-trigger player playback after session resumption with a reload event and synthetic mouse interactions.
• Title propagation: RRWebEventGenerator now accepts a title parameter used in reload custom events, derived from the application name.

New Utilities

• AttributeConverter: Converts untyped Map<String, Any?> dictionaries (from bridge layers like .NET MAUI) into OTel Attributes, with support for nested map flattening via dot-separated keys and typed list handling.

---

Note

Medium Risk
Moderate risk due to refactoring plugin wiring and telemetry/session replay initialization order, plus new replay export behavior (wake-up payloads) that changes network/event flow.

Overview
Refactors Android Observability + Session Replay integration to remove the LDExtendedInstrumentation/InstrumentationContributor* registration path and instead expose the OTel SessionManager from InstrumentationManager through ObservabilityClient into ObservabilityContext, which Session Replay consumes.

Session Replay is reworked into a standalone SessionReplayService that is initialized on onPluginsReady, receives identify events via a delegate-based SessionReplayHook (and new SessionReplayHookProxy for MAUI), and updates LDReplay to use a new SessionReplayServicing interface.

Replay export behavior changes by adding a title-aware RRWebEventGenerator and emitting an extra “wake up” payload (reload + synthetic interactions) after the first push to improve player resumption; also sets client_id for replay session init and adjusts identify event session selection when sessionId is missing.

Adds MAUI-friendly observability APIs: LDObserve.recordLog/recordError overloads plus AttributeConverter to turn Map<String, Any?> into OTel Attributes. Minor demo app UI tweaks (session replay header/toggle, label updates) and test updates/removals to match the new architecture.

^{Written by Cursor Bugbot for commit 27d2002. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

[cursor]

Accidentally committed debugging code in e2e app

Low Severity

The anonContext variable is defined but only referenced in a commented-out LDClient.get().identify(anonContext) call. This looks like leftover debugging/experimentation code that was accidentally included in the commit.