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
@@ -8,139 +8,38 @@ You will need to build React Native from source if you want to work on a new fea
8
8
9
9
### Prerequisites
10
10
11
-
Assuming you have the Android SDK installed, run `android` to open the Android SDK Manager.
11
+
To build from source, you need to have the Android SDK installed. If you followed the [Setting up the development environment](/docs/environment-setup) guide, you should already be set up.
12
12
13
-
Make sure you have the following installed:
13
+
There is no need to install other tools like specific version of NDK or CMake as the Android SDK will **automatically download** whatever is needed for the build from source.
14
14
15
-
1. Android SDK (find the specific version in the `compileSdkVersion` in [`build.gradle`](https://github.com/facebook/react-native/blob/main/ReactAndroid/build.gradle#L253)).
16
-
2. Android NDK
15
+
### Point your project to a nightly
17
16
18
-
#### Point Gradle to your Android SDK
19
-
20
-
**Step 1:** Set environment variables through your local shell.
21
-
22
-
:::note
23
-
Files may vary based on shell flavor. See below for examples from common shells.
24
-
:::
25
-
26
-
- bash: `.bash_profile` or `.bashrc`
27
-
- zsh: `.zprofile` or `.zshrc`
28
-
- ksh: `.profile` or `$ENV`
29
-
30
-
Example:
17
+
To use the latest fixes and features of React Native, you can update your project to use a nightly version of React Native with:
You can find the instructions to install the NDK on the [official Android NDK website](https://developer.android.com/studio/projects/install-ndk).
49
-
50
-
### Building the source
23
+
This will update your project to use a nightly version of React Native that gets released every night with the latest changes.
51
24
52
-
#### 1. Installing from the fork
25
+
###Update your project to build from source
53
26
54
-
First, you need to clone `react-native` from the repo you want to use locally inside the `node_modules` folder. For example, if you wish to build against `main` of this repo:
Update the `android/build.gradle` to make sure you're using AGP 7.x and add the highlighted lines.
27
+
Both with stable releases and nightlies, you will be consuming **precompiled** artifacts. If instead you want to switch to building from source, so you can test your changes to the framework directly, you will have to edit the `android/settings.gradle` file as follows:
Modify your `android/app/build.gradle` to use the `:ReactAndroid` project instead of the pre-compiled library, e.g. - replace `implementation 'com.facebook.react:react-native:+'` with `implementation project(':ReactAndroid')`:
If you use 3rd-party React Native modules, you need to override their dependencies so that they don't bundle the pre-compiled library. Otherwise you'll get an error while compiling:
117
-
118
-
```
119
-
Error: more than one library with package name 'com.facebook.react'
120
-
```
121
-
122
-
Modify your `android/build.gradle`, and add:
123
-
124
-
```groovy
125
-
allprojects {
126
-
repositories { /* ... */ }
127
-
128
-
configurations.all {
129
-
resolutionStrategy {
130
-
dependencySubstitution {
131
-
substitute module("com.facebook.react:react-native:+") with project(":ReactAndroid")
From the Welcome screen of Android Studio choose "Import project" and select the `android` folder of your app.
141
-
142
-
You should be able to use the _Run_ button to run your app on a device. Android Studio won't start the packager automatically, you'll need to start it by running `npm start` on the command line.
143
-
144
43
### Additional notes
145
44
146
45
Building from source can take a long time, especially for the first build, as it needs to download ~200 MB of artifacts and compile the native code.
@@ -156,92 +55,8 @@ gradle.projectsLoaded {
156
55
}
157
56
```
158
57
159
-
### Troubleshooting
160
-
161
-
Gradle build fails in `ndk-build`. See the section about `local.properties` file above.
162
-
163
-
## Publish your own version of React Native
164
-
165
-
There is a docker image that helps you build the required Android sources without installing any additional tooling (other than [Docker](https://docs.docker.com/install/)), which can be committed to a git branch as a fully functional React Native fork release.
166
-
167
-
Run this from a fork of the React Native [repo](https://github.com/facebook/react-native).
The recommended approach to working with React Native is to always update to the latest version. No support is provided on older versions and if you run into issues the contributors will always ask you to upgrade to the latest version before even looking at your particular issue.
190
-
191
-
Sometimes, though, you are temporarily stuck on an older React Native version, but you require some changes from newer versions urgently (bugfixes) without having to do a full upgrade right now. This situation should be short lived by definition and once you have the time, the real solution is to upgrade to the latest version.
192
-
193
-
With this goal of a shortlived fork of React Native in mind, you can publish your own version of React Native. The facebook/react-native repository contains all the dependencies required to be used directly as a git dependency, except for the Android React Native library binary (.aar).
194
-
195
-
## Building
196
-
197
-
This binary needs to become available in your project's `node_modules/react-native/android` folder or directly in your gradle dependency of your Android app. You can achieve this in one of two ways: Git dependency branch, Android binary dependency through Maven.
198
-
199
-
To build the .aar React Native library, you can follow the steps to build from source first to install all required tooling. Then to build the actual library, you can run the following in the root of your react-native checkout:
If you haven't used the Android NDK before or if you have a NDK version not exactly matching the required version for building React Native, this is the recommended approach.
212
-
213
-
The resulting binary can be made available to app projects in one of the two ways described below.
214
-
215
-
### Publishing to Maven/Nexus
216
-
217
-
Upload the binaries from the `android` folder to maven and point your Android app project gradle dependency for React Native to your Maven/Nexus dependency.
218
-
219
-
### Publishing to a git fork dependency
220
-
221
-
Instead of uploading to Maven/Nexus, you can add the binaries built in the previous steps to git, by changing the .gitignore and committing the binaries to your forked branch. This allows you to make your fork into a functioning git dependency for React Native app projects.
222
-
223
-
If you have changes that you want to actually merge to React Native, make them on another branch first and open a PR.
224
-
225
-
To start making your dependency branch, make sure you are on a `release/my-forked-release` branch, then merge any commits that you need from yourself or others into this branch.
226
-
227
-
:::warning
228
-
This release branch should never be merged into any other branch.
229
-
:::
230
-
231
-
```bash
232
-
# create .aar, then:
233
-
git add android --force
234
-
git commit -m 'my release commit'
235
-
git push
236
-
```
237
-
238
-
Now you can use this branch as a git dependency in your app project, by pointing your package.json dependency to this branch:
The recommended approach to working with React Native is to always update to the latest version. The support we provide for older versions is [described in our support policy](https://github.com/reactwg/react-native-releases/#releases-support-policy).
246
61
247
-
No other modifications to your dependencies should be necessary for your native changes to be included in your project.
62
+
The build from source approach should be used to end-to-end test a fix before submitting a pull request to React Native, and we're not encouraging its usages in the long run. Especially forking React Native or switching your setup to always use a build from source, will result in projects that are harder to update and generally a worse developer experience.
0 commit comments