Document the SPM migration playbook for end users

Open
#6,174 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

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.

Description

Docs React-Native

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.

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.