Upgrading to new versions of React Native will give you access to more APIs, views, developer tools and other goodies. Upgrading requires a small amount of effort, but we try to make it straightforward for you.
Upgrading your Expo project to a new version of React Native requires updating the
expo package versions in your
package.json file. Please refer to this list to find out what versions are supported. You will also need to set the correct
sdkVersion in your
See the Upgrading Expo SDK Walkthrough for up-to-date information about upgrading your project.
The React Native CLI comes with
upgrade command that provides a one-step operation to upgrade the source files with a minimum of conflicts, it internally uses rn-diff-purge project to find out which files need to be created, removed or modified.
1. Run the
upgradecommand works on top of Git by using
git applywith 3-way merge, therefore it's required to use Git in order for this to work, if you don't use Git but still want to use this solution then you can check out how to do it in the Troubleshooting section.
Run the following command to start the process of upgrading to the latest version:
You may specify a React Native version by passing an argument, e.g. to upgrade to
The project is upgraded using
git apply with 3-way merge, it may happen that you'll need to resolve a few conflicts after it's finished.
Conflicted files include delimiters which make very clear where the changes come from. For example:
You can think of "ours" as "your team" and "theirs" as "the React Native development team".
The Upgrade Helper is a web tool to help you out when upgrading your apps by providing the full set of changes happening between any two versions. It also shows comments on specific files to help understanding why that change is needed.
You first need to select from and to which version you wish to upgrade, by default the latest major versions are selected. After selecting you can click the button "Show me how to upgrade".
💡 Major updates will show an "useful content" section on the top with links to help you out when upgrading.
The first file that is shown is the
package.json, it's good to update the dependencies that are showing in there. For example, if
react appears as changes then you can install it in your project by running
The new release may contain updates to other files that are generated when you run
npx react-native init, those files are listed after the
package.json in the Upgrade Helper page. If there aren't other changes then you only need to rebuild the project to continue developing.
In case there are changes then you can either update them manually by copying and pasting from the changes in the page or you can do it with the React Native CLI upgrade command by running:
This will check your files against the latest template and perform the following:
- If there is a new file in the template, it is created.
- If a file in the template is identical to your file, it is skipped.
- If a file is different in your project than the template, you will be prompted; you have options to keep your file or overwrite it with the template version.
Some upgrades won't be done automatically with the React Native CLI and require manual work, e.g.
0.57. Make sure to check the release notes when upgrading so that you can identify any manual changes your particular project may require.
While your project does not have to be handled by the Git versioning system -- you can use Mercurial, SVN, or nothing -- you will still need to install Git on your system in order to use
npx react-native upgrade. Git will also need to be available in the
PATH. If your project doesn't use Git, initialize it and commit:
After you finish upgrading you may remove the
These sort of errors are usually related to caching, it's recommended to install react-native-clean-project to clear all your project's cache and then you can run it again.