You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should add CI checks to verify that the SDK builds and links on tvOS and visionOS.
Scope
tvOS — RN supports it via react-native-tvos; already declared in RNSentry.podspec (s.tvos.deployment_target).
visionOS — RN supports it via @callstack/react-native-visionos; already declared in RNSentry.podspec (s.visionos.deployment_target).
watchOS is out of scope
There is no React Native platform fork for watchOS, and the watchOS runtime has no JS engine for RN to run on. The podspec correctly omits watchos.deployment_target. A watchOS app is a pure-native target — users who want Sentry there add sentry-cocoa directly to their WatchKit target (bridged to the RN iPhone app via WatchConnectivity), which is already covered by sentry-cocoa's own CI. Nothing in @sentry/react-native runs on watchOS, so there is nothing for us to build-check.
Approach
A build-only gate (xcodebuild build with CODE_SIGNING_ALLOWED=NO) that compiles/links RNSentry against each platform, rather than a ported XCTest suite. RNSentry depends on React headers, so a standalone pod lib lint won't prove it — we need a sample app to build against.
Activity
linear-code commentedon Sep 1, 2026
RN-751
[-]Add CI checks for tvOS, visionOS or watchOS[/-][+]Add CI checks for tvOS and visionOS[/+]github-actions commentedon Sep 10, 2026
A PR closing this issue has just been released 🚀
This issue was referenced by PR #6676, which was included in the 8.26.0 release.