Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Migrate iOS enableUnhandledCPPExceptionsV2 off the deprecated experimental alias

未关闭
#6,783 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@antonis 已经在做这个了。

开始于 2026年9月24日。

评估

这个 Issue 还没有评估数据。

描述

React-Native

Description

sentry-cocoa #9134 promotes enableUnhandledCPPExceptionsV2 from SentryOptions.experimental up to a top-level SentryOptions property. The old experimental.enableUnhandledCPPExceptionsV2 is kept as a shared-value deprecated alias and, per the deprecation annotation, will be removed in the next cocoa minor release.

The RN SDK reads and writes this option in packages/core/ios/RNSentryExperimentalOptions.m:

sentryOptions.experimental.enableUnhandledCPPExceptionsV2 = enabled;   // setter
return sentryOptions.experimental.enableUnhandledCPPExceptionsV2;       // getter

Impact

  • At the cocoa release that ships #9134 (a v9 minor): RN still compiles and behaves identically — the alias shares the same backing value — but these two lines will emit deprecation warnings (the ObjC property gains DEPRECATED_MSG_ATTRIBUTE).
  • At the following cocoa minor, where the alias is removed: sentryOptions.experimental.enableUnhandledCPPExceptionsV2 will fail to compile.

We currently bundle cocoa 9.29.0, so there is no runtime breakage today. This is a tracking issue to migrate ahead of the removal.

Action

Switch to the top-level property (exposed on the ObjC wrapper SentryObjCOptions.h) at the next cocoa bump that contains #9134:

sentryOptions.enableUnhandledCPPExceptionsV2 = enabled;
return sentryOptions.enableUnhandledCPPExceptionsV2;
  • Behavior is identical; the top-level property exists in the same release, so this also clears the deprecation warning immediately.
  • The JS _experiments.enableUnhandledCPPExceptionsV2 key and RN's public API stay unchanged — this is purely the native mapping in RNSentryExperimentalOptions.m.

References

主要语言
TypeScript
星标
1.8k
派生
367
平均合并
1 天 1 小时
30 天内合并 PR
100

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

getsentry/sentry-react-native 的其他 Issue

查看 getsentry/sentry-react-native 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。