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

Remove deprecated `enableExperimentalViewRenderer` replay option in v9

Open Beginner friendly
#6,680 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
react-native, typescript
Domain
mobile-dev

Research direction

Start in packages/core/src/js/replay/mobilereplay.ts, checking the MobileReplayOptions type, defaultOptions, and mobileReplayIntegration compatibility shim identified in the issue. Then locate related tests and adjust them for the v9 behavior. Done means the deprecated option and mapping are removed, enableViewRendererV2 remains supported, and the related tests pass.

Written by the indexing model from the issue text.

Description

React-Native Replays Task

Summary

The MobileReplayOptions.enableExperimentalViewRenderer option was deprecated in favor of enableViewRendererV2 in #4815 (2025-05). A compat shim in mobileReplayIntegration copies the old value to enableViewRendererV2 when the new option is unset.

Per the SDK Deprecation Lifecycle Standard, this should be removed in the next major (v9).

Action for v9

In packages/core/src/js/replay/mobilereplay.ts:

  • Remove the enableExperimentalViewRenderer type definition (MobileReplayOptions, ~line 77).
  • Remove it from defaultOptions (~line 253).
  • Remove the compat shim that maps it onto enableViewRendererV2 (~lines 270-271).
  • Update/adjust any related tests.

References

  • Deprecated in #4815 (ref(session-replay): iOS: Use enableViewRendererV2 instead of the deprecated ...)
  • Replacement: enableViewRendererV2
  • Sibling v9 removal task: #5882
  • SDK Deprecation Lifecycle Standard
Dominant language
TypeScript
Stars
1.8k
Forks
369
Avg merge
20h 53m
Merged PRs (30d)
103

Getting set up

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.