Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Populate trace_ids in mobile replay events to enable searching replays by trace ID

Open
#6,232 1 comment 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

Assessment

This issue has not been assessed yet.

Description

Feature React-Native Replays State: Blocked

Problem

When searching for replays by trace ID in Sentry's Explore UI, mobile replays from React Native are not discoverable. While web replay (via JS SDK) collects trace_ids, the mobile replay integration does not.

Solution

The mobileReplayIntegration should collect trace IDs when transactions are captured and pass them to the native replay system.

Reference implementations
Key points
  • Collect trace IDs when transactions are successfully captured during replay recording
  • Limit to max 100 trace IDs per segment (matching JS SDK)
  • Need a bridge mechanism to pass trace IDs from JS transactions to native replay
  • Android native SDK (sentry-java) now supports registerTraceId() — need similar support in iOS (sentry-cocoa)
Dependencies
  • sentry-cocoa needs to implement trace_ids support first (or in parallel)

Action taken on behalf of Roman Zavarnitsyn.

Dominant language
TypeScript
Stars
1.8k
Forks
367
Avg merge
1d 4h
Merged PRs (30d)
102

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/sentry-react-native

All issues in getsentry/sentry-react-native

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.