getsentry / getsentry/sentry-react-native

Document the SPM migration playbook for end users

Open
#6,174 2 comments 1 reaction 0 assignees View on GitHub
Docs React-Native
Dominant language
TypeScript
Stars
1.8k
Forks
367
Avg merge
1d 6h
Merged PRs (30d)
94

Description

Once RNSentry publishes a `Package.swift` and the React Native ecosystem supports SPM autolinking, end users will need clear guidance on:

* Whether to use CocoaPods or SPM for a given app.
* How to migrate an existing CocoaPods-based app to SPM.
* What the support matrix looks like (which RN versions support each path).
* What to do with Expo apps, brownfield iOS apps, and edge cases.

Without explicit guidance, users will hit the transition in an ad hoc way and surface confused support tickets to us.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the planned RNSentry Package.swift and the React Native ecosystem's SPM autolinking support. Document the CocoaPods-versus-SPM choice, migration steps, RN-version support matrix, and guidance for Expo, brownfield iOS apps, and edge cases; the playbook is done when these paths are explicit for end users.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, react-native
Domain
documentation, mobile
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.