You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Unity SDK currently lacks proper trace ID propagation from the managed (C#) layer to the underlying native SDKs (Cocoa, Android, Native). This creates disconnected traces across different layers of the application, making it difficult to correlate events. There is no way to connect C# errors prior to a native event outside of breadcrumb messages.
Current Status by Platform
Native SDK
❌ No propagation context available on the scope
❌ Missing functionality to set trace context on the scope
❌ No continue trace API implementation
Impact: Events from native crashes cannot be correlated with their originating managed traces
Extend NDK Scope Observer to handle trace ID propagation
Test and validate Java-Native trace consistency
Validate that no integration automatically updates the trace ID on certain lifecycle events and/or disable those OOTB
Cocoa SDK:
Implement continue trace API
Update bridge to use continue trace
Validate that no integration automatically updates the trace ID on certain lifecycle events and/or disable those OOTB
Expected Outcome
After implementation, all events (managed and native) should maintain consistent trace IDs throughout the entire crash reporting pipeline. This enables proper event correlation across all layers of Unity games.
The text was updated successfully, but these errors were encountered:
Problem Statement
The Unity SDK currently lacks proper trace ID propagation from the managed (C#) layer to the underlying native SDKs (Cocoa, Android, Native). This creates disconnected traces across different layers of the application, making it difficult to correlate events. There is no way to connect C# errors prior to a native event outside of breadcrumb messages.
Current Status by Platform
Native SDK
continue trace
API implementationAndroid SDK
Cocoa SDK
continue trace
APIStep by Step
Native SDK -
set_trace_id
to continue trace sentry-native#1137continue trace
APIAndroid SDK:
Cocoa SDK:
continue trace
APIcontinue trace
Expected Outcome
After implementation, all events (managed and native) should maintain consistent trace IDs throughout the entire crash reporting pipeline. This enables proper event correlation across all layers of Unity games.
The text was updated successfully, but these errors were encountered: