Remove deprecated `_experiments.androidProfilingOptions` in v9

Open
#6,681 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the listed locations in packages/core/src/js/options.ts, client.ts, and wrapper.ts, then inspect related tests for androidProfilingOptions and profilingOptions. Confirm the deprecated type, fallback, parameter, and compatibility resolution are removed for v9 while the replacement profilingOptions path remains covered by passing tests.

Written by the indexing model from the issue text.

Description

Profiles React-Native Task

Summary

The _experiments.androidProfilingOptions option was deprecated in favor of _experiments.profilingOptions in #5611 (2026-02). Its JSDoc already states it "will be removed in the next major version." Fallback code currently resolves profilingOptions ?? androidProfilingOptions for backwards compatibility.

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

Action for v9

  • packages/core/src/js/options.ts (~line 499): remove the androidProfilingOptions type definition from the _experiments block.
  • packages/core/src/js/client.ts (~line 255): drop the ?? this._options._experiments?.androidProfilingOptions fallback.
  • packages/core/src/js/wrapper.ts (~lines 67, 309, 316-317): remove the androidProfilingOptions parameter and the profilingOptions ?? androidProfilingOptions compat resolution.
  • Update/adjust any related tests.

References

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

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.