react-native/docs/RunningOnDeviceIOS.md

---
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](/react-native/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.
Add docs about running on device 2015-04-02 17:41:22 +00:00			`---`
[docs] Make it clear which Guides are platform-specific This is in preparation for open sourcing React Native for Android. Also add hyphens to URLs for consistency. This can break people's browser bookmarks but it's better to be consistent and we can redirect to docs: https://github.com/facebook/react-native/issues/2137 Test plan: Ran the website locally using `cd website; npm start` and checked all pages render correctly. http://i.imgur.com/RrPNgRr.png Will update "Getting Started", "Tutorial", "Debugging" and "Testing" separately. 2015-07-27 17:03:46 +00:00			`id: running-on-device-ios`
Split iOS and Android docs into different categories 2015-09-18 17:54:05 +00:00			`title: Running On Device`
Add docs about running on device 2015-04-02 17:41:22 +00:00			`layout: docs`
Split iOS and Android docs into different categories 2015-09-18 17:54:05 +00:00			`category: Guides (iOS)`
[docs] Make it clear which Guides are platform-specific This is in preparation for open sourcing React Native for Android. Also add hyphens to URLs for consistency. This can break people's browser bookmarks but it's better to be consistent and we can redirect to docs: https://github.com/facebook/react-native/issues/2137 Test plan: Ran the website locally using `cd website; npm start` and checked all pages render correctly. http://i.imgur.com/RrPNgRr.png Will update "Getting Started", "Tutorial", "Debugging" and "Testing" separately. 2015-07-27 17:03:46 +00:00			`permalink: docs/running-on-device-ios.html`
Split iOS and Android docs into different categories 2015-09-18 17:54:05 +00:00			`next: embedded-app-ios`
Add docs about running on device 2015-04-02 17:41:22 +00:00			`---`

Fix link to Apple Developer account registration. 2015-08-04 21:07:42 +00:00			`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.`
Add docs about running on device 2015-04-02 17:41:22 +00:00
			`## 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.`

fix AppDelegate.m path 2015-09-19 20:56:21 +00:00			1. Open `AwesomeApp/ios/AwesomeApp/AppDelegate.m`
Update RunningOnDeviceIOS.md 2015-10-17 09:26:58 +00:00			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.
Add docs about running on device 2015-04-02 17:41:22 +00:00			`3. In Xcode select your phone as build target and press "Build and run"`

			`> Hint`
			`>`
Update RunningOnDevice.md - Misspell correction 2015-04-03 14:38:47 +00:00			`> Shake the device to open development menu (reload, debug, etc.)`
Add docs about running on device 2015-04-02 17:41:22 +00:00
			`## 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.`

fix AppDelegate.m path 2015-09-19 20:56:21 +00:00			1. Open `AwesomeApp/ios/AwesomeApp/AppDelegate.m`
Add docs about running on device 2015-04-02 17:41:22 +00:00			`2. Follow the instructions for "OPTION 2":`
			* Uncomment `jsCodeLocation = [[NSBundle mainBundle] ...`
give a more detailed bundle example 2016-01-13 03:35:01 +00:00			* 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
Add docs about running on device 2015-04-02 17:41:22 +00:00
Updated docs to reflect bundle script 2015-04-21 00:00:39 +00:00			`The bundle script supports a couple of flags:`
Add docs about running on device 2015-04-02 17:41:22 +00:00
Clarify --dev flag for react-native-bundle Given some [confusion around `react-native bundle`'s `--dev` flag][1], this hopes to clear somet things up int he docs by… - Removing mentions of the `__DEV__` environment variable - I think it confuses the user on how to work with the command-line flag, and frankly it seems like an internal implementation detail from the perspective of react-native-cli. We should focus on what the `--dev` flag does (e.g., toggles dev warnings, performance optimizations). - Adding a minimal note about native-land's build configurations and how that should be checked for production builds [1]: https://github.com/facebook/react-native/issues/4181 2015-11-23 13:20:20 +00:00			* `--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.
Updated docs to reflect bundle script 2015-04-21 00:00:39 +00:00			* `--minify` - pipe the JS code through UglifyJS.
Add docs about running on device 2015-04-02 17:41:22 +00:00
Update RunningOnDeviceIOS.md 2015-10-13 19:08:11 +00:00			Note that on 0.14 we'll change the API of `react-native bundle`. The major changes are:
Update RunningOnDeviceIOS.md 2015-10-13 19:41:42 +00:00
Update RunningOnDeviceIOS.md 2015-10-13 19:08:11 +00:00			* 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>`

[Docs] Clean up debugging docs 2015-04-29 23:59:50 +00:00			`## 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](/react-native/docs/debugging.html#debugging-react-native-apps) in order to disable the in-app developer menu.

Add docs about running on device 2015-04-02 17:41:22 +00:00			`## 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.