Let's upgrade our React Native project

Vinieratos says React Native upgrades require work across JavaScript, iOS, and Android, including Xcode projects, Gradle scripts, and libraries with native code. Expo can avoid native work at first, but apps that need an unsupported native feature may have to eject. He notes that React Native releases used to arrive every two weeks, then monthly, and later around major features.

Vinieratos describes rn-diff-purge as a collection of generated diffs that lets developers compare any starting version with any destination version. The Upgrade Helper presents those changes in a web interface with file-by-file diffs, notes, and links to release information. The `npx react-native upgrade` command can apply changes, but template diffs may fail when a project has different files or customizations.

Vinieratos recommends reading release notes, trying the CLI, and using Upgrade Helper to review changes one file at a time. He suggests handling package and configuration updates first, then reviewing native files and checking whether template files apply to the app. Developers should confirm their custom setup and libraries support the target version, then test the application.

Vinieratos demonstrates copying relevant Android and iOS changes while skipping files that a project does not use. He calls the Xcode project file especially difficult: generated IDs vary, so developers should focus on meaningful names and project structure rather than copying IDs exactly. He recommends asking an iOS teammate for help when that file changes.

Vinieratos advises doing easy changes first, choosing only the changes relevant to the app, and upgrading regularly when possible. If a team has fallen several months behind, he suggests moving one version at a time or at least one minor version at a time. He says upgrades have become more specific and manageable, while inviting developers to report problems and contribute fixes.