Populate trace_ids in replay events to enable searching replays by trace ID (converted to project)

[sentry-junior]

This issue has been converted to a project Populate trace_ids in replay events to enable searching replays by trace ID

---

When searching for replays by trace ID in Sentry's Explore UI, Android replays are now discoverable (getsentry/sentry-java#5473), but iOS replays are not. This is because SentryReplayEvent doesn't collect or include trace_ids.

Solution

Similar to sentry-javascript and sentry-java, when a transaction is captured while replay is recording, the trace ID should be registered with the replay system and included in the next replay segment's trace_ids field.

Reference implementations

• JS: https://github.com/getsentry/sentry-javascript/blob/30eb68fff5077211c30c61ba74625e66ab514870/packages/replay-internal/src/coreHandlers/handleAfterSendEvent.ts#L34-L43
• Java: fix(replay): Associate trace IDs with replay segments sentry-java#5473

Key points

• Collect trace IDs when transactions are successfully captured during replay recording
• Limit to max 100 trace IDs per segment (matching JS SDK)
• Clear collected trace IDs after each segment is sent

Action taken on behalf of Roman Zavarnitsyn.

[linear-code]

COCOA-1444