feat: MAUI API revamp

[abelonogov-ld]

Summary

• Adds the new LDObserve.Init(...) API format with two entry points:
  • LDObserve.Init(mobileKey, observabilityOptions, sessionReplayOptions) for standalone initialization.
  • LDObserve.Init(client, observabilityOptions, sessionReplayOptions) for LaunchDarkly client-backed initialization.
• Consolidates observability and session replay under a single ObservabilityPlugin, removing the separate session replay plugin and the fragile plugin orchestrator.
• Updates the sample app and README to use explicit ObservabilityOptions and optional SessionReplayOptions instead of registering plugins through PluginConfigurationBuilder.

Details

• LDNative is now internal and called through LDObserve.Init.
• SessionReplayOptions is optional; when omitted, replay is not wired up.
• Standalone initialization now wires the LDObserve facade so RecordLog, metrics, spans, and errors work without an LdClient.
• HTTP activity propagation is centralized in ObservabilityService, so network tracing is enabled consistently across both initialization paths.
• README examples now show the new client and standalone setup formats, including session replay privacy and instrumentation options.

Testing

• Verified edited files with IDE lints.
• Manually reviewed the sample initialization path for both standalone and LdClient variants.
• Full MAUI/iOS/Android build not run in this session.

---

Note

Medium Risk
Public MAUI initialization API and plugin registration change (breaking for integrators on the old dual-plugin pattern); native init parameter renames affect multiple bindings but are mechanical.

Overview
The .NET MAUI observability package moves to a single LDObserve.Init entry point instead of registering separate ObservabilityPlugin / SessionReplayPlugin on LdClient. Init(mobileKey, …) starts the native stack without a feature-flag client; Init(client, …) registers one combined ObservabilityPlugin that boots native code and wires observability + replay hooks. PluginOrchestrator, SessionReplayPlugin, and INativePlugin are removed; LDReplay.IsEnabled replaces sample MauiProgram.LdNative for toggling replay.

Native LDObserve.init call sites (Android e2e, Flutter, MAUI bridge) rename parameters from options/replayOptions to observability/replay. Docs and the sample app follow the new API; package version bumps to 0.11.0 and LaunchDarkly.ClientSdk to [5.8.0, 6.0.0); iOS binding sets SupportedOSPlatformVersion 15.0.

^{Reviewed by Cursor Bugbot for commit 86e97a7. Bugbot is set up for automated code reviews on this repo. Configure here.}

[Vadman97]

should this be a feat! major bump? or are we still on 0.x, then we are ok

[cursor]

Cursor Bugbot has reviewed your changes using default effort 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.}

^{Reviewed by Cursor Bugbot for commit 79aae6e. Configure here.}

[cursor]

Pre-init buffer applies pending value after native bridge starts

Medium Severity

LDReplay.OnNativeStarted (which calls Bind to apply buffered IsEnabled writes) is invoked AFTER bridge.Start has already consumed the replay options. On Android, options are converted via ToNative() before Bind runs, so pending values never reach native. On iOS, the bridge reads initial values during Start. A user who sets LDReplay.IsEnabled = false before init expects native replay to start disabled, but the native layer starts with the original value because Bind applies too late.

Additional Locations (1)

• sdk/@launchdarkly/mobile-dotnet/observability/replay/api/PreInitReplayBuffer.cs#L50-L61

 

^{Reviewed by Cursor Bugbot for commit 79aae6e. Configure here.}