859 lines
34 KiB
Markdown
859 lines
34 KiB
Markdown
---
|
||
id: integration-with-existing-apps
|
||
title: Integration With Existing Apps
|
||
layout: docs
|
||
category: Guides
|
||
permalink: docs/integration-with-existing-apps.html
|
||
banner: ejected
|
||
next: running-on-device
|
||
previous: testing
|
||
---
|
||
|
||
<div class="integration-toggler">
|
||
<style>
|
||
.integration-toggler a {
|
||
display: inline-block;
|
||
padding: 10px 5px;
|
||
margin: 2px;
|
||
border: 1px solid #05A5D1;
|
||
border-radius: 3px;
|
||
text-decoration: none !important;
|
||
}
|
||
.display-platform-objc .integration-toggler .button-objc,
|
||
.display-platform-swift .integration-toggler .button-swift,
|
||
.display-platform-android .integration-toggler .button-android {
|
||
background-color: #05A5D1;
|
||
color: white;
|
||
}
|
||
block { display: none; }
|
||
.display-platform-objc .objc,
|
||
.display-platform-swift .swift,
|
||
.display-platform-android .android {
|
||
display: block;
|
||
}</style>
|
||
<span>Platform:</span>
|
||
<a href="javascript:void(0);" class="button-objc" onclick="display('platform', 'objc')">Objective-C</a>
|
||
<a href="javascript:void(0);" class="button-swift" onclick="display('platform', 'swift')">Swift</a>
|
||
<a href="javascript:void(0);" class="button-android" onclick="display('platform', 'android')">Android</a>
|
||
</div>
|
||
|
||
<block class="android" />
|
||
|
||
> This section will be updated shortly showing an integration into a more real world application such as the 2048 app that was used for Objective-C and Swift.
|
||
|
||
<block class="objc swift android" />
|
||
|
||
## Key Concepts
|
||
|
||
React Native is great when you are starting a new mobile app from scratch. However, it also works well for adding a single view or user flow to existing native applications. With a few steps, you can add new React Native based features, screens, views, etc.
|
||
|
||
<block class="objc swift" />
|
||
|
||
The keys to integrating React Native components into your iOS application are to:
|
||
|
||
1. Understand what React Native components you want to integrate.
|
||
2. Create a `Podfile` with `subspec`s for all the React Native components you will need for your integration.
|
||
3. Create your actual React Native components in JavaScript.
|
||
4. Add a new event handler that creates a `RCTRootView` that points to your React Native component and its `AppRegistry` name that you defined in `index.ios.js`.
|
||
5. Start the React Native server and run your native application.
|
||
6. Optionally add more React Native components.
|
||
7. [Debug](/react-native/releases/next/docs/debugging.html).
|
||
8. Prepare for [deployment](docs/running-on-device.html) (e.g., via the `react-native-xcode.sh` script).
|
||
9. Deploy and Profit!
|
||
|
||
<block class="android" />
|
||
|
||
The keys to integrating React Native components into your Android application are to:
|
||
|
||
1. Understand what React Native components you want to integrate.
|
||
2. Install `react-native` in your Android application root directory to create `node_modules/` directory.
|
||
3. Create your actual React Native components in JavaScript.
|
||
4. Add `com.facebook.react:react-native:+` and a `maven` pointing to the `react-native` binaries in `node_modules/` to your `build.gradle` file.
|
||
4. Create a custom React Native specific `Activity` that creates a `ReactRootView`.
|
||
5. Start the React Native server and run your native application.
|
||
6. Optionally add more React Native components.
|
||
7. [Debug](/react-native/releases/next/docs/debugging.html).
|
||
8. [Prepare](/react-native/releases/next/docs/signed-apk-android.html) for [deployment](docs/running-on-device.html).
|
||
9. Deploy and Profit!
|
||
|
||
<block class="objc swift android" />
|
||
|
||
## Prerequisites
|
||
|
||
<block class="android" />
|
||
|
||
The [Android Getting Started guide](docs/getting-started.html) will install the appropriate prerequisites (e.g., `npm`) for React Native on the Android target platform and your chosen development environment.
|
||
|
||
> To ensure a smooth experience, make sure your `android` project is under `$root/android`.
|
||
|
||
<block class="objc swift" />
|
||
|
||
### General
|
||
|
||
First, follow the [Getting Started guide](docs/getting-started.html) for your development environment and the iOS target platform to install the prerequisites for React Native.
|
||
|
||
> To ensure a smooth experience, make sure your `iOS` project is under `$root/ios`.
|
||
|
||
### CocoaPods
|
||
|
||
[CocoaPods](http://cocoapods.org) is a package management tool for iOS and Mac development. We use it to add the actual React Native framework code locally into your current project.
|
||
|
||
```bash
|
||
$ sudo gem install cocoapods
|
||
```
|
||
|
||
> It is technically possible not to use CocoaPods, but this requires manual library and linker additions that overly complicates this process.
|
||
|
||
## Our Sample App
|
||
|
||
<block class="objc" />
|
||
|
||
Assume the [app for integration](https://github.com/JoelMarcey/iOS-2048) is a [2048](https://en.wikipedia.org/wiki/2048_%28video_game%29) game. Here is what the main menu of the native application looks like without React Native.
|
||
|
||
<block class="swift" />
|
||
|
||
Assume the [app for integration](https://github.com/JoelMarcey/swift-2048) is a [2048](https://en.wikipedia.org/wiki/2048_%28video_game%29) game. Here is what the main menu of the native application looks like without React Native.
|
||
|
||
<block class="objc swift" />
|
||
|
||
|
||
|
||
## Package Dependencies
|
||
|
||
React Native integration requires both the React and React Native node modules. The React Native Framework will provide the code to allow your application integration to happen.
|
||
|
||
|
||
### `package.json`
|
||
|
||
We will add the package dependencies to a `package.json` file. Create this file in the root of your project if it does not exist.
|
||
|
||
> Normally with React Native projects, you will put files like `package.json`, `index.ios.js`, etc. in the root directory of your project and then have your iOS specific native code in a subdirectory like `ios/` where your Xcode project is located (e.g., `.xcodeproj`).
|
||
|
||
Below is an example of what your `package.json` file should minimally contain.
|
||
|
||
> Version numbers will vary according to your needs. Normally the latest versions for both [React](https://github.com/facebook/react/releases) and [React Native](https://github.com/facebook/react-native/releases) will be sufficient.
|
||
|
||
<block class="objc" />
|
||
|
||
```bash
|
||
{
|
||
"name": "NumberTileGame",
|
||
"version": "0.0.1",
|
||
"private": true,
|
||
"scripts": {
|
||
"start": "node node_modules/react-native/local-cli/cli.js start"
|
||
},
|
||
"dependencies": {
|
||
"react": "15.0.2",
|
||
"react-native": "0.26.1"
|
||
}
|
||
}
|
||
```
|
||
|
||
<block class="swift" />
|
||
|
||
```bash
|
||
{
|
||
"name": "swift-2048",
|
||
"version": "0.0.1",
|
||
"private": true,
|
||
"scripts": {
|
||
"start": "node node_modules/react-native/local-cli/cli.js start"
|
||
},
|
||
"dependencies": {
|
||
"react": "15.0.2",
|
||
"react-native": "0.26.1"
|
||
}
|
||
}
|
||
```
|
||
|
||
<block class="objc swift" />
|
||
|
||
### Packages Installation
|
||
|
||
Install the React and React Native modules via the Node package manager. The Node modules will be installed into a `node_modules/` directory in the root of your project.
|
||
|
||
```bash
|
||
# From the directory containing package.json project, install the modules
|
||
# The modules will be installed in node_modules/
|
||
$ npm install
|
||
```
|
||
|
||
## React Native Framework
|
||
|
||
The React Native Framework was installed as Node module in your project [above](#package-dependencies). We will now install a CocoaPods `Podfile` with the components you want to use from the framework itself.
|
||
|
||
### Subspecs
|
||
|
||
Before you integrate React Native into your application, you will want to decide what parts of the React Native Framework you would like to integrate. That is where `subspec`s come in. When you create your `Podfile`, you are going to specify React Native library dependencies that you will want installed so that your application can use those libraries. Each library will become a `subspec` in the `Podfile`.
|
||
|
||
|
||
The list of supported `subspec`s are in [`node_modules/react-native/React.podspec`](https://github.com/facebook/react-native/blob/master/React.podspec). They are generally named by functionality. For example, you will generally always want the `Core` `subspec`. That will get you the `AppRegistry`, `StyleSheet`, `View` and other core React Native libraries. If you want to add the React Native `Text` library (e.g., for `<Text>` elements), then you will need the `RCTText` `subspec`. If you want the `Image` library (e.g., for `<Image>` elements), then you will need the `RCTImage` `subspec`.
|
||
|
||
#### Podfile
|
||
|
||
After you have used Node to install the React and React Native frameworks into the `node_modules` directory, and you have decided on what React Native elements you want to integrate, you are ready to create your `Podfile` so you can install those components for use in your application.
|
||
|
||
The easiest way to create a `Podfile` is by using the CocoaPods `init` command in the native iOS code directory of your project:
|
||
|
||
```bash
|
||
## In the directory where your native iOS code is located (e.g., where your `.xcodeproj` file is located)
|
||
$ pod init
|
||
```
|
||
|
||
The `Podfile` will be created and saved in the *iOS* directory (e.g., `ios/`) of your current project and will contain a boilerplate setup that you will tweak for your integration purposes. In the end, `Podfile` should look something similar to this:
|
||
|
||
<block class="objc" />
|
||
|
||
```
|
||
# The target name is most likely the name of your project.
|
||
target 'NumberTileGame' do
|
||
|
||
# Your 'node_modules' directory is probably in the root of your project,
|
||
# but if not, adjust the `:path` accordingly
|
||
pod 'React', :path => '../node_modules/react-native', :subspecs => [
|
||
'Core',
|
||
'RCTText',
|
||
'RCTNetwork',
|
||
'RCTWebSocket', # needed for debugging
|
||
# Add any other subspecs you want to use in your project
|
||
]
|
||
# Explicitly include Yoga if you are using RN >= 0.42.0
|
||
pod "Yoga", :path => "../node_modules/react-native/ReactCommon/yoga"
|
||
|
||
end
|
||
```
|
||
|
||
<block class="swift" />
|
||
|
||
```
|
||
source 'https://github.com/CocoaPods/Specs.git'
|
||
|
||
# Required for Swift apps
|
||
platform :ios, '8.0'
|
||
use_frameworks!
|
||
|
||
# The target name is most likely the name of your project.
|
||
target 'swift-2048' do
|
||
|
||
# Your 'node_modules' directory is probably in the root of your project,
|
||
# but if not, adjust the `:path` accordingly
|
||
pod 'React', :path => '../node_modules/react-native', :subspecs => [
|
||
'Core',
|
||
'RCTText',
|
||
'RCTNetwork',
|
||
'RCTWebSocket', # needed for debugging
|
||
# Add any other subspecs you want to use in your project
|
||
]
|
||
# Explicitly include Yoga if you are using RN >= 0.42.0
|
||
pod "Yoga", :path => "../node_modules/react-native/ReactCommon/yoga"
|
||
|
||
end
|
||
```
|
||
|
||
<block class="objc swift" />
|
||
|
||
#### Pod Installation
|
||
|
||
After you have created your `Podfile`, you are ready to install the React Native pod.
|
||
|
||
```bash
|
||
$ pod install
|
||
```
|
||
|
||
Your should see output such as:
|
||
|
||
```bash
|
||
Analyzing dependencies
|
||
Fetching podspec for `React` from `../node_modules/react-native`
|
||
Downloading dependencies
|
||
Installing React (0.26.0)
|
||
Generating Pods project
|
||
Integrating client project
|
||
Sending stats
|
||
Pod installation complete! There are 3 dependencies from the Podfile and 1 total pod installed.
|
||
```
|
||
|
||
<block class="swift" />
|
||
|
||
> If you get a warning such as "*The `swift-2048 [Debug]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-swift-2048/Pods-swift-2048.debug.xcconfig`. This can lead to problems with the CocoaPods installation*", then make sure the `Framework Search Paths` in `Build Settings` for both `Debug` and `Release` only contain `$(inherited)`.
|
||
|
||
<block class="objc swift" />
|
||
|
||
## Code Integration
|
||
|
||
Now that we have a package foundation, we will actually modify the native application to integrate React Native into the application. For our 2048 app, we will add a "High Score" screen in React Native.
|
||
|
||
### The React Native component
|
||
|
||
The first bit of code we will write is the actual React Native code for the new "High Score" screen that will be integrated into our application.
|
||
|
||
#### Create a `index.ios.js` file
|
||
|
||
First, create an empty `index.ios.js` file. For ease, I am doing this in the root of the project.
|
||
|
||
> `index.ios.js` is the starting point for React Native applications on iOS. And it is always required. It can be a small file that `require`s other file that are part of your React Native component or application, or it can contain all the code that is needed for it. In our case, we will just put everything in `index.ios.js`
|
||
|
||
```bash
|
||
# In root of your project
|
||
$ touch index.ios.js
|
||
```
|
||
|
||
#### Add Your React Native Code
|
||
|
||
In your `index.ios.js`, create your component. In our sample here, we will add simple `<Text>` component within a styled `<View>`
|
||
|
||
```js
|
||
'use strict';
|
||
|
||
import React from 'react';
|
||
import {
|
||
AppRegistry,
|
||
StyleSheet,
|
||
Text,
|
||
View
|
||
} from 'react-native';
|
||
|
||
class RNHighScores extends React.Component {
|
||
render() {
|
||
var contents = this.props["scores"].map(
|
||
score => <Text key={score.name}>{score.name}:{score.value}{"\n"}</Text>
|
||
);
|
||
return (
|
||
<View style={styles.container}>
|
||
<Text style={styles.highScoresTitle}>
|
||
2048 High Scores!
|
||
</Text>
|
||
<Text style={styles.scores}>
|
||
{contents}
|
||
</Text>
|
||
</View>
|
||
);
|
||
}
|
||
}
|
||
|
||
const styles = StyleSheet.create({
|
||
container: {
|
||
flex: 1,
|
||
justifyContent: 'center',
|
||
alignItems: 'center',
|
||
backgroundColor: '#FFFFFF',
|
||
},
|
||
highScoresTitle: {
|
||
fontSize: 20,
|
||
textAlign: 'center',
|
||
margin: 10,
|
||
},
|
||
scores: {
|
||
textAlign: 'center',
|
||
color: '#333333',
|
||
marginBottom: 5,
|
||
},
|
||
});
|
||
|
||
// Module name
|
||
AppRegistry.registerComponent('RNHighScores', () => RNHighScores);
|
||
```
|
||
|
||
> `RNHighScores` is the name of your module that will be used when you add a view to React Native from within your iOS application.
|
||
|
||
## The Magic: `RCTRootView`
|
||
|
||
Now that your React Native component is created via `index.ios.js`, you need to add that component to a new or existing `ViewController`. The easiest path to take is to optionally create an event path to your component and then add that component to an existing `ViewController`.
|
||
|
||
We will tie our React Native component with a new native view in the `ViewController` that will actually host it called `RCTRootView` .
|
||
|
||
### Create an Event Path
|
||
|
||
You can add a new link on the main game menu to go to the "High Score" React Native page.
|
||
|
||
|
||
|
||
#### Event Handler
|
||
|
||
We will now add an event handler from the menu link. A method will be added to the main `ViewController` of your application. This is where `RCTRootView` comes into play.
|
||
|
||
When you build a React Native application, you use the React Native packager to create an `index.ios.bundle` that will be served by the React Native server. Inside `index.ios.bundle` will be our `RNHighScore` module. So, we need to point our `RCTRootView` to the location of the `index.ios.bundle` resource (via `NSURL`) and tie it to the module.
|
||
|
||
We will, for debugging purposes, log that the event handler was invoked. Then, we will create a string with the location of our React Native code that exists inside the `index.ios.bundle`. Finally, we will create the main `RCTRootView`. Notice how we provide `RNHighScores` as the `moduleName` that we created [above](#the-react-native-component) when writing the code for our React Native component.
|
||
|
||
<block class="objc" />
|
||
|
||
First `import` the `RCTRootView` header.
|
||
|
||
```
|
||
#import <React/RCTRootView.h>
|
||
```
|
||
|
||
> The `initialProperties` are here for illustration purposes so we have some data for our high score screen. In our React Native component, we will use `this.props` to get access to that data.
|
||
|
||
```
|
||
- (IBAction)highScoreButtonPressed:(id)sender {
|
||
NSLog(@"High Score Button Pressed");
|
||
NSURL *jsCodeLocation = [NSURL
|
||
URLWithString:@"http://localhost:8081/index.ios.bundle?platform=ios"];
|
||
RCTRootView *rootView =
|
||
[[RCTRootView alloc] initWithBundleURL : jsCodeLocation
|
||
moduleName : @"RNHighScores"
|
||
initialProperties :
|
||
@{
|
||
@"scores" : @[
|
||
@{
|
||
@"name" : @"Alex",
|
||
@"value": @"42"
|
||
},
|
||
@{
|
||
@"name" : @"Joel",
|
||
@"value": @"10"
|
||
}
|
||
]
|
||
}
|
||
launchOptions : nil];
|
||
UIViewController *vc = [[UIViewController alloc] init];
|
||
vc.view = rootView;
|
||
[self presentViewController:vc animated:YES completion:nil];
|
||
}
|
||
```
|
||
|
||
> Note that `RCTRootView initWithURL` starts up a new JSC VM. To save resources and simplify the communication between RN views in different parts of your native app, you can have multiple views powered by React Native that are associated with a single JS runtime. To do that, instead of using `[RCTRootView alloc] initWithURL`, use [`RCTBridge initWithBundleURL`](https://github.com/facebook/react-native/blob/master/React/Base/RCTBridge.h#L93) to create a bridge and then use `RCTRootView initWithBridge`.
|
||
|
||
<block class="swift" />
|
||
|
||
First `import` the `React` library.
|
||
|
||
```
|
||
import React
|
||
```
|
||
|
||
> The `initialProperties` are here for illustration purposes so we have some data for our high score screen. In our React Native component, we will use `this.props` to get access to that data.
|
||
|
||
```
|
||
@IBAction func highScoreButtonTapped(sender : UIButton) {
|
||
NSLog("Hello")
|
||
let jsCodeLocation = URL(string: "http://localhost:8081/index.ios.bundle?platform=ios")
|
||
let mockData:NSDictionary = ["scores":
|
||
[
|
||
["name":"Alex", "value":"42"],
|
||
["name":"Joel", "value":"10"]
|
||
]
|
||
]
|
||
|
||
let rootView = RCTRootView(
|
||
bundleURL: jsCodeLocation,
|
||
moduleName: "RNHighScores",
|
||
initialProperties: mockData as [NSObject : AnyObject],
|
||
launchOptions: nil
|
||
)
|
||
let vc = UIViewController()
|
||
vc.view = rootView
|
||
self.present(vc, animated: true, completion: nil)
|
||
}
|
||
```
|
||
|
||
> Note that `RCTRootView bundleURL` starts up a new JSC VM. To save resources and simplify the communication between RN views in different parts of your native app, you can have multiple views powered by React Native that are associated with a single JS runtime. To do that, instead of using `RCTRootView bundleURL`, use [`RCTBridge initWithBundleURL`](https://github.com/facebook/react-native/blob/master/React/Base/RCTBridge.h#L93) to create a bridge and then use `RCTRootView initWithBridge`.
|
||
|
||
<block class="objc" />
|
||
|
||
> When moving your app to production, the `NSURL` can point to a pre-bundled file on disk via something like `[[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];`. You can use the `react-native-xcode.sh` script in `node_modules/react-native/packager/` to generate that pre-bundled file.
|
||
|
||
<block class="swift" />
|
||
|
||
> When moving your app to production, the `NSURL` can point to a pre-bundled file on disk via something like `let mainBundle = NSBundle(URLForResource: "main" withExtension:"jsbundle")`. You can use the `react-native-xcode.sh` script in `node_modules/react-native/packager/` to generate that pre-bundled file.
|
||
|
||
<block class="objc swift" />
|
||
|
||
#### Wire Up
|
||
|
||
Wire up the new link in the main menu to the newly added event handler method.
|
||
|
||
|
||
|
||
> One of the easier ways to do this is to open the view in the storyboard and right click on the new link. Select something such as the `Touch Up Inside` event, drag that to the storyboard and then select the created method from the list provided.
|
||
|
||
## Test Your Integration
|
||
|
||
You have now done all the basic steps to integrate React Native with your current application. Now we will start the React Native packager to build the `index.ios.bundle` packager and the server running on `localhost` to serve it.
|
||
|
||
### App Transport Security
|
||
|
||
Apple has blocked implicit cleartext HTTP resource loading. So we need to add the following our project's `Info.plist` (or equivalent) file.
|
||
|
||
```xml
|
||
<key>NSAppTransportSecurity</key>
|
||
<dict>
|
||
<key>NSExceptionDomains</key>
|
||
<dict>
|
||
<key>localhost</key>
|
||
<dict>
|
||
<key>NSTemporaryExceptionAllowsInsecureHTTPLoads</key>
|
||
<true/>
|
||
</dict>
|
||
</dict>
|
||
</dict>
|
||
```
|
||
|
||
### Run the Packager
|
||
|
||
```bash
|
||
# From the root of your project, where the `node_modules` directory is located.
|
||
$ npm start
|
||
```
|
||
|
||
### Run the App
|
||
|
||
If you are using Xcode or your favorite editor, build and run your native iOS application as normal. Alternatively, you can run the app from the command line using:
|
||
|
||
```bash
|
||
# From the root of your project
|
||
$ react-native run-ios
|
||
```
|
||
|
||
In our sample application, you should see the link to the "High Scores" and then when you click on that you will see the rendering of your React Native component.
|
||
|
||
Here is the *native* application home screen:
|
||
|
||
|
||
|
||
Here is the *React Native* high score screen:
|
||
|
||
|
||
|
||
> If you are getting module resolution issues when running your application please see [this GitHub issue](https://github.com/facebook/react-native/issues/4968) for information and possible resolution. [This comment](https://github.com/facebook/react-native/issues/4968#issuecomment-220941717) seemed to be the latest possible resolution.
|
||
|
||
### See the Code
|
||
|
||
<block class="objc" />
|
||
|
||
You can examine the code that added the React Native screen on [GitHub](https://github.com/JoelMarcey/iOS-2048/commit/9ae70c7cdd53eb59f5f7c7daab382b0300ed3585).
|
||
|
||
<block class="swift" />
|
||
|
||
You can examine the code that added the React Native screen on [GitHub](https://github.com/JoelMarcey/swift-2048/commit/13272a31ee6dd46dc68b1dcf4eaf16c1a10f5229).
|
||
|
||
<block class="android" />
|
||
|
||
## Add JS to your app
|
||
|
||
In your app's root folder, run:
|
||
|
||
$ npm init
|
||
$ npm install --save react react-native
|
||
$ curl -o .flowconfig https://raw.githubusercontent.com/facebook/react-native/master/.flowconfig
|
||
|
||
This creates a node module for your app and adds the `react-native` npm dependency. Now open the newly created `package.json` file and add this under `scripts`:
|
||
|
||
"start": "node node_modules/react-native/local-cli/cli.js start"
|
||
|
||
Copy & paste the following code to `index.android.js` in your root folder — it's a barebones React Native app:
|
||
|
||
```js
|
||
'use strict';
|
||
|
||
import React from 'react';
|
||
import {
|
||
AppRegistry,
|
||
StyleSheet,
|
||
Text,
|
||
View
|
||
} from 'react-native';
|
||
|
||
class HelloWorld extends React.Component {
|
||
render() {
|
||
return (
|
||
<View style={styles.container}>
|
||
<Text style={styles.hello}>Hello, World</Text>
|
||
</View>
|
||
)
|
||
}
|
||
}
|
||
var styles = StyleSheet.create({
|
||
container: {
|
||
flex: 1,
|
||
justifyContent: 'center',
|
||
},
|
||
hello: {
|
||
fontSize: 20,
|
||
textAlign: 'center',
|
||
margin: 10,
|
||
},
|
||
});
|
||
|
||
AppRegistry.registerComponent('HelloWorld', () => HelloWorld);
|
||
```
|
||
|
||
## Prepare your current app
|
||
|
||
In your app's `build.gradle` file add the React Native dependency:
|
||
```
|
||
dependencies {
|
||
...
|
||
compile "com.facebook.react:react-native:+" // From node_modules.
|
||
}
|
||
```
|
||
|
||
> If you want to ensure that you are always using a specific React Native version in your native build, replace `+` with an actual React Native version you've downloaded from `npm`.
|
||
|
||
In your project's `build.gradle` file add an entry for the local React Native maven directory. Be sure to add it to the "allprojects" block:
|
||
|
||
```
|
||
allprojects {
|
||
repositories {
|
||
...
|
||
maven {
|
||
// All of React Native (JS, Android binaries) is installed from npm
|
||
url "$rootDir/node_modules/react-native/android"
|
||
}
|
||
}
|
||
...
|
||
}
|
||
```
|
||
|
||
> Make sure that the path is correct! You shouldn’t run into any “Failed to resolve: com.facebook.react:react-native:0.x.x" errors after running Gradle sync in Android Studio.
|
||
|
||
Next, make sure you have the Internet permission in your `AndroidManifest.xml`:
|
||
|
||
<uses-permission android:name="android.permission.INTERNET" />
|
||
|
||
If you need to access to the `DevSettingsActivity` add to your `AndroidManifest.xml`:
|
||
|
||
<activity android:name="com.facebook.react.devsupport.DevSettingsActivity" />
|
||
|
||
This is only really used in dev mode when reloading JavaScript from the development server, so you can strip this in release builds if you need to.
|
||
|
||
## Add native code
|
||
|
||
You need to add some native code in order to start the React Native runtime and get it to render something. To do this, we're going to create an `Activity` that creates a `ReactRootView`, starts a React application inside it and sets it as the main content view.
|
||
|
||
> If you are targetting Android version <5, use the `AppCompatActivity` class from the `com.android.support:appcompat` package instead of `Activity`.
|
||
|
||
```java
|
||
public class MyReactActivity extends Activity implements DefaultHardwareBackBtnHandler {
|
||
private ReactRootView mReactRootView;
|
||
private ReactInstanceManager mReactInstanceManager;
|
||
|
||
@Override
|
||
protected void onCreate(Bundle savedInstanceState) {
|
||
super.onCreate(savedInstanceState);
|
||
|
||
mReactRootView = new ReactRootView(this);
|
||
mReactInstanceManager = ReactInstanceManager.builder()
|
||
.setApplication(getApplication())
|
||
.setBundleAssetName("index.android.bundle")
|
||
.setJSMainModuleName("index.android")
|
||
.addPackage(new MainReactPackage())
|
||
.setUseDeveloperSupport(BuildConfig.DEBUG)
|
||
.setInitialLifecycleState(LifecycleState.RESUMED)
|
||
.build();
|
||
mReactRootView.startReactApplication(mReactInstanceManager, "HelloWorld", null);
|
||
|
||
setContentView(mReactRootView);
|
||
}
|
||
|
||
@Override
|
||
public void invokeDefaultOnBackPressed() {
|
||
super.onBackPressed();
|
||
}
|
||
}
|
||
```
|
||
> If you are using a starter kit for React Native, replace the "HelloWorld" string with the one in your index.android.js file (it’s the first argument to the `AppRegistry.registerComponent()` method).
|
||
|
||
If you are using Android Studio, use `Alt + Enter` to add all missing imports in your MyReactActivity class. Be careful to use your package’s `BuildConfig` and not the one from the `...facebook...` package.
|
||
|
||
We need set the theme of `MyReactActivity` to `Theme.AppCompat.Light.NoActionBar` because some components rely on this theme.
|
||
```xml
|
||
<activity
|
||
android:name=".MyReactActivity"
|
||
android:label="@string/app_name"
|
||
android:theme="@style/Theme.AppCompat.Light.NoActionBar">
|
||
</activity>
|
||
```
|
||
|
||
|
||
|
||
> A `ReactInstanceManager` can be shared amongst multiple activities and/or fragments. You will want to make your own `ReactFragment` or `ReactActivity` and have a singleton *holder* that holds a `ReactInstanceManager`. When you need the `ReactInstanceManager` (e.g., to hook up the `ReactInstanceManager` to the lifecycle of those Activities or Fragments) use the one provided by the singleton.
|
||
|
||
Next, we need to pass some activity lifecycle callbacks down to the `ReactInstanceManager`:
|
||
|
||
```java
|
||
@Override
|
||
protected void onPause() {
|
||
super.onPause();
|
||
|
||
if (mReactInstanceManager != null) {
|
||
mReactInstanceManager.onHostPause(this);
|
||
}
|
||
}
|
||
|
||
@Override
|
||
protected void onResume() {
|
||
super.onResume();
|
||
|
||
if (mReactInstanceManager != null) {
|
||
mReactInstanceManager.onHostResume(this, this);
|
||
}
|
||
}
|
||
|
||
@Override
|
||
protected void onDestroy() {
|
||
super.onDestroy();
|
||
|
||
if (mReactInstanceManager != null) {
|
||
mReactInstanceManager.onHostDestroy();
|
||
}
|
||
}
|
||
```
|
||
|
||
We also need to pass back button events to React Native:
|
||
|
||
```java
|
||
@Override
|
||
public void onBackPressed() {
|
||
if (mReactInstanceManager != null) {
|
||
mReactInstanceManager.onBackPressed();
|
||
} else {
|
||
super.onBackPressed();
|
||
}
|
||
}
|
||
```
|
||
|
||
This allows JavaScript to control what happens when the user presses the hardware back button (e.g. to implement navigation). When JavaScript doesn't handle a back press, your `invokeDefaultOnBackPressed` method will be called. By default this simply finishes your `Activity`.
|
||
|
||
Finally, we need to hook up the dev menu. By default, this is activated by (rage) shaking the device, but this is not very useful in emulators. So we make it show when you press the hardware menu button (use `Ctrl + M` if you're using Android Studio emulator):
|
||
|
||
```java
|
||
@Override
|
||
public boolean onKeyUp(int keyCode, KeyEvent event) {
|
||
if (keyCode == KeyEvent.KEYCODE_MENU && mReactInstanceManager != null) {
|
||
mReactInstanceManager.showDevOptionsDialog();
|
||
return true;
|
||
}
|
||
return super.onKeyUp(keyCode, event);
|
||
}
|
||
```
|
||
|
||
Now your activity is ready to run some JavaScript code.
|
||
|
||
### Configure permissions for development error overlay
|
||
|
||
If your app is targeting the Android `API level 23` or greater, make sure you have the `overlay` permission enabled for the development build. You can check it with `Settings.canDrawOverlays(this);`. This is required in dev builds because react native development errors must be displayed above all the other windows. Due to the new permissions system introduced in the API level 23, the user needs to approve it. This can be achieved by adding the following code to the Activity file in the onCreate() method. OVERLAY_PERMISSION_REQ_CODE is a field of the class which would be responsible for passing the result back to the Activity.
|
||
|
||
```java
|
||
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
|
||
if (!Settings.canDrawOverlays(this)) {
|
||
Intent intent = new Intent(Settings.ACTION_MANAGE_OVERLAY_PERMISSION,
|
||
Uri.parse("package:" + getPackageName()));
|
||
startActivityForResult(intent, OVERLAY_PERMISSION_REQ_CODE);
|
||
}
|
||
}
|
||
```
|
||
|
||
Finally, the `onActivityResult()` method (as shown in the code below) has to be overridden to handle the permission Accepted or Denied cases for consistent UX.
|
||
|
||
```java
|
||
@Override
|
||
protected void onActivityResult(int requestCode, int resultCode, Intent data) {
|
||
if (requestCode == OVERLAY_PERMISSION_REQ_CODE) {
|
||
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
|
||
if (!Settings.canDrawOverlays(this)) {
|
||
// SYSTEM_ALERT_WINDOW permission not granted...
|
||
}
|
||
}
|
||
}
|
||
}
|
||
```
|
||
|
||
## Run your app
|
||
|
||
To run your app, you need to first start the development server. To do this, simply run the following command in your root folder:
|
||
|
||
$ npm start
|
||
|
||
Now build and run your Android app as normal (`./gradlew installDebug` from command-line; in Android Studio just create debug build as usual).
|
||
|
||
> If you are using Android Studio for your builds and not the Gradle Wrapper directly, make sure you install [watchman](https://facebook.github.io/watchman/) before running `npm start`. It will prevent the packager from crashing due to conflicts between Android Studio and the React Native packager.
|
||
|
||
Once you reach your React-powered activity inside the app, it should load the JavaScript code from the development server and display:
|
||
|
||
|
||
|
||
<script>
|
||
// Convert <div>...<span><block /></span>...</div>
|
||
// Into <div>...<block />...</div>
|
||
var blocks = document.getElementsByTagName('block');
|
||
for (var i = 0; i < blocks.length; ++i) {
|
||
var block = blocks[i];
|
||
var span = blocks[i].parentNode;
|
||
var container = span.parentNode;
|
||
container.insertBefore(block, span);
|
||
container.removeChild(span);
|
||
}
|
||
// Convert <div>...<block />content<block />...</div>
|
||
// Into <div>...<block>content</block><block />...</div>
|
||
blocks = document.getElementsByTagName('block');
|
||
for (var i = 0; i < blocks.length; ++i) {
|
||
var block = blocks[i];
|
||
while (block.nextSibling && block.nextSibling.tagName !== 'BLOCK') {
|
||
block.appendChild(block.nextSibling);
|
||
}
|
||
}
|
||
function display(type, value) {
|
||
var container = document.getElementsByTagName('block')[0].parentNode;
|
||
container.className = 'display-' + type + '-' + value + ' ' +
|
||
container.className.replace(RegExp('display-' + type + '-[a-z]+ ?'), '');
|
||
console.log(container.className);
|
||
event && event.preventDefault();
|
||
}
|
||
|
||
// If we are coming to the page with a hash in it (i.e. from a search, for example), try to get
|
||
// us as close as possible to the correct platform and dev os using the hashtag and block walk up.
|
||
var foundHash = false;
|
||
if (window.location.hash !== '' && window.location.hash !== 'content') { // content is default
|
||
var hashLinks = document.querySelectorAll('a.hash-link');
|
||
for (var i = 0; i < hashLinks.length && !foundHash; ++i) {
|
||
if (hashLinks[i].hash === window.location.hash) {
|
||
var parent = hashLinks[i].parentElement;
|
||
while (parent) {
|
||
if (parent.tagName === 'BLOCK') {
|
||
var targetPlatform = null;
|
||
// Could be more than one target platform, but just choose some sort of order
|
||
// of priority here.
|
||
|
||
// Target Platform
|
||
if (parent.className.indexOf('objc') > -1) {
|
||
targetPlatform = 'objc';
|
||
} else if (parent.className.indexOf('swift') > -1) {
|
||
targetPlatform = 'swift';
|
||
} else if (parent.className.indexOf('android') > -1) {
|
||
targetPlatform = 'android';
|
||
} else {
|
||
break; // assume we don't have anything.
|
||
}
|
||
// We would have broken out if both targetPlatform and devOS hadn't been filled.
|
||
display('platform', targetPlatform);
|
||
foundHash = true;
|
||
break;
|
||
}
|
||
parent = parent.parentElement;
|
||
}
|
||
}
|
||
}
|
||
}
|
||
// Do the default if there is no matching hash
|
||
if (!foundHash) {
|
||
var isMac = navigator.platform === 'MacIntel';
|
||
display('platform', isMac ? 'objc' : 'android');
|
||
}
|
||
</script>
|
||
|
||
<block class="android" />
|
||
|
||
## Creating a release build in Android Studio
|
||
|
||
You can use Android Studio to create your release builds too! It’s as easy as creating release builds of your previously-existing native Android app. There’s just one additional step, which you’ll have to do before every release build. You need to execute the following to create a React Native bundle, which’ll be included with your native Android app:
|
||
|
||
$ react-native bundle --platform android --dev false --entry-file index.android.js --bundle-output android/com/your-company-name/app-package-name/src/main/assets/index.android.bundle --assets-dest android/com/your-company-name/app-package-name/src/main/res/
|
||
|
||
Don’t forget to replace the paths with correct ones and create the assets folder if it doesn’t exist!
|
||
|
||
Now just create a release build of your native app from within Android Studio as usual and you should be good to go!
|