feat: MAUI integration hooks and refactor for 0.4.1 nuget

[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
Refactors plugin wiring and session replay export behavior (session manager capture, identify flow, and extra payload pushes), which can impact initialization order and replay delivery if assumptions differ across apps.

Overview
Refactors the Android Observability + Session Replay integration to remove the old InstrumentationContributor/InstrumentationContributorManager + LDExtendedInstrumentation registration path, and instead capture/expose the OTel SessionManager via an AndroidInstrumentation bridge (ObservabilityClient.sessionManager → ObservabilityContext.sessionManager). The log pipeline in InstrumentationManager is simplified by dropping per-instrumentation log routing.

Session Replay is reworked around a standalone SessionReplayService (ReplayInstrumentation → SessionReplayService, ReplayControl → SessionReplayServicing): the SessionReplay plugin now constructs the service directly, initializes it on onPluginsReady(), and routes SDK identify events through a delegate-based SessionReplayHook plus a new bridge-friendly SessionReplayHookProxy/LDReplay.hookProxy. Replay exporting adds app title propagation, sets client_id, sends identify events even when session id is missing by falling back to the last capture session, and may emit an additional “wake-up” payload (reload + synthetic interactions) to resume playback.

Adds AttributeConverter and LDObserve overloads to accept MAUI-friendly Map<String, Any?> attributes and severity numbers without exposing OpenTelemetry types. Also includes small demo app UI tweaks (Session Replay header/toggle) and updated tests for the new wiring and extra replay payload.

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

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

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

[cursor]

shouldWakeUpSession not restored during export rollback

Medium Severity

The export method snapshots and restores lastCaptureState, payloadIdCounter, pushedCanvasSize, and eventGenerator state on failure, but shouldWakeUpSession is not included. If wakeUpEvents succeeds (setting shouldWakeUpSession = false) but a subsequent session's pushPayload throws, the outer catch rolls back all other state while shouldWakeUpSession stays false. On retry, wake-up events are never re-sent and the rolled-back payloadIdCounter reuses IDs that the already-sent wake-up events consumed.

Additional Locations (1)

• sdk/@launchdarkly/observability-android/lib/src/main/kotlin/com/launchdarkly/observability/replay/exporter/SessionReplayExporter.kt#L69-L137