mirror of
https://github.com/facebook/react-native.git
synced 2025-11-01 09:14:26 +00:00
Konstantin Raev
afcef0154e
Summary: Copy of #5760 reverted merge. We need to preserve history of docs changes on the webserver. The goal is to allow users to browse outdated versions of docs. To make things simple all websites will be released to https://facebook.github.io/react-native/releases/version/XX folder when there is a branch cut. I switched from Travis CI to Cirle CI because it works faster and I am more familiar with it. How it works: 1. If code is pushed to `master` branch then CI will build a fresh version of docs and put it in https://github.com/facebook/react-native/tree/gh-pages/releases/next folder. Github will serve this website from https://facebook.github.io/react-native/releases/version/next URL. All relative URLs will work within that website 2. If code is pushed to `0.20-stable` branch then CI will build a fresh version of docs and put it in https://github.com/facebook/react-native/tree/gh-pages/releases/0.20 folder. Github will serve this website from https://facebook.github.io/react-native/releases/v Closes https://github.com/facebook/react-native/pull/5873 Reviewed By: svcscm Differential Revision: D2926901 Pulled By: androidtrunkagent fb-gh-sync-id: 16aea430bac815933d9c603f03921cc6353906f1 shipit-source-id: 16aea430bac815933d9c603f03921cc6353906f1 Conflicts: Libraries/Utilities/AlertIOS.js circle.yml website/layout/AutodocsLayout.js
54 lines
2.9 KiB
Markdown
54 lines
2.9 KiB
Markdown
---
|
|
id: running-on-device-ios
|
|
title: Running On Device
|
|
layout: docs
|
|
category: Guides (iOS)
|
|
permalink: docs/running-on-device-ios.html
|
|
next: embedded-app-ios
|
|
---
|
|
|
|
Note that running on device requires [Apple Developer account](https://developer.apple.com/register) and provisioning your iPhone. This guide covers only React Native specific topic.
|
|
|
|
## Accessing development server from device
|
|
|
|
You can iterate quickly on device using development server. To do that, your laptop and your phone have to be on the same wifi network.
|
|
|
|
1. Open `AwesomeApp/ios/AwesomeApp/AppDelegate.m`
|
|
2. Change the IP in the URL from `localhost` to your laptop's IP. On Mac, you can find the IP address in System Preferences / Network.
|
|
3. In Xcode select your phone as build target and press "Build and run"
|
|
|
|
> Hint
|
|
>
|
|
> Shake the device to open development menu (reload, debug, etc.)
|
|
|
|
## Using offline bundle
|
|
|
|
You can also pack all the JavaScript code within the app itself. This way you can test it without development server running and submit the app to the AppStore.
|
|
|
|
1. Open `AwesomeApp/ios/AwesomeApp/AppDelegate.m`
|
|
2. Follow the instructions for "OPTION 2":
|
|
* Uncomment `jsCodeLocation = [[NSBundle mainBundle] ...`
|
|
* Run the `react-native bundle --platform ios --dev false --entry-file index.ios.js --bundle-output iOS/main.jsbundle` command in terminal from the root directory of your app
|
|
|
|
The bundle script supports a couple of flags:
|
|
|
|
* `--dev` - a boolean with a default value of `true`. With the `--dev true` flag, the bundled JavaScript code turns on useful development warnings and limits performance optimizations. For production it is recommended to pass `--dev false`. Also for production, be sure to have your native build configuration set to `Release` (e.g., Xcode's Release configuration for iOS and gradle's `assembleRelease` task for Android) in order to disable things like the shake-to-show developer menu.
|
|
* `--minify` - pipe the JS code through UglifyJS.
|
|
|
|
Note that on 0.14 we'll change the API of `react-native bundle`. The major changes are:
|
|
|
|
* API is now `entry-file <path>` based instead of url based.
|
|
* Need to specify which platform you're bundling for `--platform <ios|android>`.
|
|
* Option `--out` has been renamed for `--bundle-output`.
|
|
* Source maps are no longer automatically generated. Need to specify `--sourcemap-output <path>`
|
|
|
|
## Disabling in-app developer menu
|
|
|
|
When building your app for production, your app's scheme should be set to `Release` as detailed in [the debugging documentation](docs/debugging.html#debugging-react-native-apps) in order to disable the in-app developer menu.
|
|
|
|
## Troubleshooting
|
|
|
|
If `curl` command fails make sure the packager is running. Also try adding `--ipv4` flag to the end of it.
|
|
|
|
If you started your project a while ago, `main.jsbundle` might not be included into Xcode project. To add it, right click on your project directory and click "Add Files to ..." - choose the `main.jsbundle` file that you generated.
|