822 lines
31 KiB
Markdown
822 lines
31 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: colors
|
||
---
|
||
|
||
<style>
|
||
.toggler li {
|
||
display: inline-block;
|
||
position: relative;
|
||
top: 1px;
|
||
padding: 10px;
|
||
margin: 0px 2px 0px 2px;
|
||
border: 1px solid #05A5D1;
|
||
border-bottom-color: transparent;
|
||
border-radius: 3px 3px 0px 0px;
|
||
color: #05A5D1;
|
||
background-color: transparent;
|
||
font-size: 0.99em;
|
||
cursor: pointer;
|
||
}
|
||
.toggler li:first-child {
|
||
margin-left: 0;
|
||
}
|
||
.toggler li:last-child {
|
||
margin-right: 0;
|
||
}
|
||
.toggler ul {
|
||
width: 100%;
|
||
display: inline-block;
|
||
list-style-type: none;
|
||
margin: 0;
|
||
border-bottom: 1px solid #05A5D1;
|
||
cursor: default;
|
||
}
|
||
@media screen and (max-width: 960px) {
|
||
.toggler li,
|
||
.toggler li:first-child,
|
||
.toggler li:last-child {
|
||
display: block;
|
||
border-bottom-color: #05A5D1;
|
||
border-radius: 3px;
|
||
margin: 2px 0px 2px 0px;
|
||
}
|
||
.toggler ul {
|
||
border-bottom: 0;
|
||
}
|
||
}
|
||
.toggler a {
|
||
display: inline-block;
|
||
padding: 10px 5px;
|
||
margin: 2px;
|
||
border: 1px solid #05A5D1;
|
||
border-radius: 3px;
|
||
text-decoration: none !important;
|
||
}
|
||
.display-language-objc .toggler .button-objc,
|
||
.display-language-swift .toggler .button-swift,
|
||
.display-language-android .toggler .button-android {
|
||
background-color: #05A5D1;
|
||
color: white;
|
||
}
|
||
block { display: none; }
|
||
.display-language-objc .objc,
|
||
.display-language-swift .swift,
|
||
.display-language-android .android {
|
||
display: block;
|
||
}
|
||
</style>
|
||
|
||
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.
|
||
|
||
The specific steps are different depending on what platform you're targeting.
|
||
|
||
<div class="toggler">
|
||
<ul role="tablist" >
|
||
<li id="objc" class="button-objc" aria-selected="false" role="tab" tabindex="0" aria-controls="objctab" onclick="displayTab('language', 'objc')">
|
||
iOS (Objective-C)
|
||
</li>
|
||
<li id="swift" class="button-swift" aria-selected="false" role="tab" tabindex="0" aria-controls="swifttab" onclick="displayTab('language', 'swift')">
|
||
iOS (Swift)
|
||
</li>
|
||
<li id="android" class="button-android" aria-selected="false" role="tab" tabindex="0" aria-controls="androidtab" onclick="displayTab('language', 'android')">
|
||
Android (Java)
|
||
</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<block class="objc swift android" />
|
||
|
||
## Key Concepts
|
||
|
||
<block class="objc swift" />
|
||
|
||
The keys to integrating React Native components into your iOS application are to:
|
||
|
||
1. Set up React Native dependencies and directory structure.
|
||
2. Understand what React Native components you will use in your app.
|
||
3. Add these components as dependencies using CocoaPods.
|
||
4. Develop your React Native components in JavaScript.
|
||
5. Add a `RCTRootView` to your iOS app. This view will serve as the container for your React Native component.
|
||
6. Start the React Native server and run your native application.
|
||
7. Verify that the React Native aspect of your application works as expected.
|
||
|
||
<block class="android" />
|
||
|
||
The keys to integrating React Native components into your Android application are to:
|
||
|
||
1. Set up React Native dependencies and directory structure.
|
||
2. Develop your React Native components in JavaScript.
|
||
3. Add a `ReactRootView` to your Android app. This view will serve as the container for your React Native component.
|
||
4. Start the React Native server and run your native application.
|
||
5. Verify that the React Native aspect of your application works as expected.
|
||
|
||
<block class="objc swift android" />
|
||
|
||
## Prerequisites
|
||
|
||
<block class="objc swift" />
|
||
|
||
Follow the instructions for building apps with native code from the [Getting Started guide](docs/getting-started.html) to configure your development environment for building React Native apps for iOS.
|
||
|
||
### 1. Set up directory structure
|
||
|
||
To ensure a smooth experience, create a new folder for your integrated React Native project, then copy your existing iOS project to a `/ios` subfolder.
|
||
|
||
<block class="android" />
|
||
|
||
Follow the instructions for building apps with native code from the [Getting Started guide](docs/getting-started.html) to configure your development environment for building React Native apps for Android.
|
||
|
||
### 1. Set up directory structure
|
||
|
||
To ensure a smooth experience, create a new folder for your integrated React Native project, then copy your existing Android project to a `/android` subfolder.
|
||
|
||
<block class="objc swift android" />
|
||
|
||
### 2. Install JavaScript dependencies
|
||
|
||
Go to the root directory for your project and create a new `package.json` file with the following contents:
|
||
|
||
```
|
||
{
|
||
"name": "MyReactNativeApp",
|
||
"version": "0.0.1",
|
||
"private": true,
|
||
"scripts": {
|
||
"start": "node node_modules/react-native/local-cli/cli.js start"
|
||
}
|
||
}
|
||
```
|
||
|
||
Next, you will install the `react` and `react-native` packages. Open a terminal or command prompt, then navigate to the root directory for your project and type the following commands:
|
||
|
||
```
|
||
$ npm install --save react react-native
|
||
```
|
||
|
||
This will create a new `/node_modules` folder in your project's root directory. This folder stores all the JavaScript dependencies required to build your project.
|
||
|
||
<block class="objc swift" />
|
||
|
||
### 3. Install CocoaPods
|
||
|
||
[CocoaPods](http://cocoapods.org) is a package management tool for iOS and macOS development. We use it to add the actual React Native framework code locally into your current project.
|
||
|
||
We recommend installing CocoaPods using [Homebrew](http://brew.sh/).
|
||
|
||
```
|
||
$ brew install cocoapods
|
||
```
|
||
|
||
> It is technically possible not to use CocoaPods, but that would require manual library and linker additions that would overly complicate this process.
|
||
|
||
<block class="objc swift" />
|
||
|
||
## Adding React Native to your 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" />
|
||
|
||
|
||
|
||
### Configuring CocoaPods dependencies
|
||
|
||
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. We will use CocoaPods to specify which of these "subspecs" your app will depend on.
|
||
|
||
The list of supported `subspec`s is available 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`.
|
||
|
||
You can specify which `subspec`s your app will depend on in a `Podfile` file. The easiest way to create a `Podfile` is by running the CocoaPods `init` command in the `/ios` subfolder of your project:
|
||
|
||
```
|
||
$ pod init
|
||
```
|
||
|
||
The `Podfile` 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',
|
||
'DevSupport', # Include this to enable In-App Devmenu if RN >= 0.43
|
||
'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',
|
||
'CxxBridge', # Include this for RN >= 0.47
|
||
'DevSupport', # Include this to enable In-App Devmenu if RN >= 0.43
|
||
'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" />
|
||
|
||
After you have created your `Podfile`, you are ready to install the React Native pod.
|
||
|
||
```
|
||
$ pod install
|
||
```
|
||
|
||
You should see output such as:
|
||
|
||
```
|
||
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 we will actually modify the native iOS application to integrate React Native. For our 2048 sample 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.
|
||
|
||
##### 1. Create a `index.js` file
|
||
|
||
First, create an empty `index.js` file in the root of your React Native project.
|
||
|
||
`index.js` is the starting point for React Native applications, 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.js`.
|
||
|
||
##### 2. Add your React Native code
|
||
|
||
In your `index.js`, create your component. In our sample here, we will add simple `<Text>` component within a styled `<View>`
|
||
|
||
```javascript
|
||
'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('MyReactNativeApp', () => 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.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` .
|
||
|
||
##### 1. Create an Event Path
|
||
|
||
You can add a new link on the main game menu to go to the "High Score" React Native page.
|
||
|
||
|
||
|
||
##### 2. 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.bundle` that will be served by the React Native server. Inside `index.bundle` will be our `RNHighScore` module. So, we need to point our `RCTRootView` to the location of the `index.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.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.
|
||
|
||
```objectivec
|
||
#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.
|
||
|
||
```objectivec
|
||
- (IBAction)highScoreButtonPressed:(id)sender {
|
||
NSLog(@"High Score Button Pressed");
|
||
NSURL *jsCodeLocation = [NSURL URLWithString:@"http://localhost:8081/index.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.
|
||
|
||
```javascript
|
||
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.
|
||
|
||
```swift
|
||
@IBAction func highScoreButtonTapped(sender : UIButton) {
|
||
NSLog("Hello")
|
||
let jsCodeLocation = URL(string: "http://localhost:8081/index.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#L89) 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/scripts/` 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/scripts/` to generate that pre-bundled file.
|
||
|
||
<block class="objc swift" />
|
||
|
||
##### 3. 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.bundle` package and the server running on `localhost` to serve it.
|
||
|
||
##### 1. Add App Transport Security exception
|
||
|
||
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>
|
||
```
|
||
|
||
> App Transport Security is good for your users. Make sure to re-enable it prior to releasing your app for production.
|
||
|
||
##### 2. Run the packager
|
||
|
||
To run your app, you need to first start the development server. To do this, simply run the following command in the root directory of your React Native project:
|
||
|
||
```
|
||
$ npm start
|
||
```
|
||
|
||
##### 3. 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:
|
||
|
||
```
|
||
# 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 to our sample app on [GitHub](https://github.com/JoelMarcey/iOS-2048/commit/9ae70c7cdd53eb59f5f7c7daab382b0300ed3585).
|
||
|
||
<block class="swift" />
|
||
|
||
You can examine the code that added the React Native screen to our sample app on [GitHub](https://github.com/JoelMarcey/swift-2048/commit/13272a31ee6dd46dc68b1dcf4eaf16c1a10f5229).
|
||
|
||
<block class="android" />
|
||
|
||
## Adding React Native to your app
|
||
|
||
### Configuring maven
|
||
|
||
Add the React Native dependency to your app's `build.gradle` file:
|
||
|
||
```
|
||
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`.
|
||
|
||
Add an entry for the local React Native maven directory to `build.gradle`. 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.
|
||
|
||
### Configuring permissions
|
||
|
||
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.
|
||
|
||
### Code integration
|
||
|
||
Now we will actually modify the native Android application to integrate 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.
|
||
|
||
##### 1. Create a `index.js` file
|
||
|
||
First, create an empty `index.js` file in the root of your React Native project.
|
||
|
||
`index.js` is the starting point for React Native applications, 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.js`.
|
||
|
||
##### 2. Add your React Native code
|
||
|
||
In your `index.js`, create your component. In our sample here, we will add simple `<Text>` component within a styled `<View>`:
|
||
|
||
```javascript
|
||
'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('MyReactNativeApp', () => HelloWorld);
|
||
```
|
||
|
||
##### 3. 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...
|
||
}
|
||
}
|
||
}
|
||
}
|
||
```
|
||
|
||
#### The Magic: `ReactRootView`
|
||
|
||
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")
|
||
.setJSMainModulePath("index")
|
||
.addPackage(new MainReactPackage())
|
||
.setUseDeveloperSupport(BuildConfig.DEBUG)
|
||
.setInitialLifecycleState(LifecycleState.RESUMED)
|
||
.build();
|
||
mReactRootView.startReactApplication(mReactInstanceManager, "MyReactNativeApp", 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.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.
|
||
|
||
### 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.bundle` package and the server running on localhost to serve it.
|
||
|
||
##### 1. Run the packager
|
||
|
||
To run your app, you need to first start the development server. To do this, simply run the following command in the root directory of your React Native project:
|
||
|
||
```
|
||
$ npm start
|
||
```
|
||
|
||
##### 2. Run the app
|
||
|
||
Now build and run your Android app as normal.
|
||
|
||
Once you reach your React-powered activity inside the app, it should load the JavaScript code from the development server and display:
|
||
|
||
|
||
|
||
### 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 will be included with your native Android app:
|
||
|
||
```
|
||
$ react-native bundle --platform android --dev false --entry-file index.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!
|
||
|
||
<block class="objc swift android" />
|
||
|
||
### Now what?
|
||
|
||
At this point you can continue developing your app as usual. Refer to our [debugging](docs/debugging.html) and [deployment](docs/running-on-device.html) docs to learn more about working with React Native.
|
||
|
||
<script>
|
||
function displayTab(type, value) {
|
||
var container = document.getElementsByTagName('block')[0].parentNode;
|
||
container.className = 'display-' + type + '-' + value + ' ' +
|
||
container.className.replace(RegExp('display-' + type + '-[a-z]+ ?'), '');
|
||
event && event.preventDefault();
|
||
}
|
||
</script>
|