WIP Traces

[abelonogov-ld]

Summary

How did you test this change?

Are there any deployment considerations?

---

Note

Medium Risk
Medium risk because it adds a new OpenTelemetry trace-export path from .NET to native (Android/iOS) and refactors plugin initialization/hook wiring, which can affect telemetry correctness and session replay linkage.

Overview
Adds .NET MAUI trace support by introducing an OpenTelemetry TracerProvider (LDTracer) and exporter (LDTraceExporter/TraceBuilderAdapter) that forwards completed Activity spans into the native SDK via new native tracer/SpanBuilder bridge types.

Expands the .NET native bridge to fully implement logs, errors, and metrics on Android/iOS (including attribute conversion/flattening), and refactors initialization by replacing NativePluginConnector with a centralized PluginOrchestrator plus updated hook exporters for observability and session replay.

Updates Android/iOS native layers to support the bridge (new com.launchdarkly.observability.bridge APIs, session replay afterIdentify proxy, wake-up/reload replay events, and bridge-supplied trace/span ID overrides in the span exporter), and refreshes the MAUI sample/docs (renamed README to Observability, new DialogsPage, richer log attributes, span examples, dependency/version bumps).

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

[cursor]

Wake-up failure leaks payload ID counter increment

Low Severity

wakeUpEvents calls nextPayloadId() inside its own try-catch, so if the wake-up pushPayload fails, the exception is swallowed and the outer rollback logic never executes. This means payloadIdCounter keeps its incremented value even though the payload was never delivered, creating a gap in the sequence of payload IDs sent to the server.

 

[cursor]

Commented-out code and unused variable in e2e app

Low Severity

anonContext is constructed but only referenced in the commented-out LDClient.get().identify(anonContext) call. This is dead code that appears to be leftover debugging or testing scaffolding from development.

 

[cursor]

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

There are 4 total unresolved issues (including 2 from previous reviews).

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

[cursor]

Exporter singleton permanently drops spans if initialized early

High Severity

LDTraceExporter captures the native tracer reference in its constructor and stores it in a readonly field. Since it's created inside the LDTracer lazy singleton, this constructor runs exactly once. If the native SDK hasn't finished initializing when LDTracer.Instance is first accessed, _adapter will be null permanently, and all C#-originated spans will be silently dropped forever (the Export method returns ExportResult.Success even when _adapter is null). The adapter lookup needs to be deferred to export time or support re-initialization.

Additional Locations (1)

• sdk/@launchdarkly/mobile-dotnet/observability/observe/api/LDTracer.cs#L15-L33

 

[cursor]

Force-unwrap on nullable sessionManager may crash

Medium Severity

capturedSessionManager!! will throw a NullPointerException if the ld-session-manager-bridge instrumentation's install callback was never invoked during rumBuilder.build(). If OpenTelemetry RUM skips the instrumentation for any reason (e.g., configuration change, initialization error), this causes an unrecoverable crash at startup. A safer approach would handle the null case gracefully.