Trace Context Status is Unknown

[philipphofmann]

Description

When the SDK serializes the trace context to puts it onto the scope

sentry-cocoa/Sources/Sentry/SentryScope.m

Lines 635 to 642 in 72a8746

	- (NSDictionary *)buildTraceContext:(nullable id<SentrySpan>)span
	{
	if (span != nil) {
	return [SENTRY_UNWRAP_NULLABLE_VALUE(id<SentrySpan>, span) serialize];
	} else {
	return [self.propagationContext traceContextForEvent];
	}
	}

sentry-cocoa/Sources/Sentry/SentrySpan.m

Lines 372 to 374 in 72a8746

	if (self.status != kSentrySpanStatusUndefined) {
	[mutableDictionary setValue:nameForSentrySpanStatus(self.status) forKey:@"status"];
	}

the default status is unkown when the trace didn't finish yet.

This confuses users when looking at the trace details when looking at events in Sentry, because they wonder why it's unknown. We need to figure out if this is by design and if yes, we should fix it to avoid user confusion.

[linear]

COCOA-692 Trace Context Status is Unknown

[philipphofmann]

According to @markushi, the same happens on Android.

[philipphofmann]

For spans first the default is OK. I think we can use the same value, as unknown is confusing, but we should do this in a major.