Updated docs for next

releases/next/docs/running-on-device.html

@@ -77,7 +77,7 @@ emulator<span class="token number">-5554</span> offline   # Google emulator
 
 </span><ol><li>Make sure your laptop and your phone are on the <strong>same</strong> Wi-Fi network.</li><li>Open your React Native app on your device.</li><li>You&#x27;ll see a <a href="/react-native/docs/debugging.html#in-app-errors-and-warnings" target="">red screen with an error</a>. This is OK. The following steps will fix that.</li><li>Open the in-app <a href="/react-native/docs/debugging.html#accessing-the-in-app-developer-menu" target="">Developer menu</a>.</li><li>Go to <strong>Dev Settings</strong> → <strong>Debug server host for device</strong>.</li><li>Type in your machine&#x27;s IP address and the port of the local dev server (e.g. 10.0.1.1:8081).</li><li>Go back to the <strong>Developer menu</strong> and select <strong>Reload JS</strong>.</li></ol><span><block class="mac ios" />
 
-</span><h2><a class="anchor" name="building-your-app-for-production"></a>Building your app for production <a class="hash-link" href="docs/running-on-device.html#building-your-app-for-production">#</a></h2><p>You have built a great app using React Native, and you are now itching to release it in the App Store. The process is the same as any other native iOS app, with some additional considerations to take into account.</p><p>Building an app for distribution in the App Store requires using the <code>Release</code> scheme in Xcode. To do this, go to <strong>Product</strong> → <strong>Scheme</strong> → <strong>Edit Scheme (cmd + &lt;)</strong>, make sure you&#x27;re in the <strong>Run</strong> tab from the side, and set the Build Configuration dropdown to <code>Release</code>.</p><p>Apps built for <code>Release</code> will automatically disable the in-app Developer menu, which will prevent your users from inadvertently accessing the menu in production. It will also load the JavaScript locally, so you can put the app on a device and test whilst not connected to the computer.</p><p>Once built for release, you&#x27;ll be able to distribute the app to beta testers and submit the app to the App Store.</p><h3><a class="anchor" name="app-transport-security"></a>App Transport Security <a class="hash-link" href="docs/running-on-device.html#app-transport-security">#</a></h3><p>App Transport Security is a security feature, added in iOS 9, that rejects all HTTP requests that are not sent over HTTPS. This can result in HTTP traffic being blocked, including the developer React Native server.</p><p>ATS is disabled by default in projects generated using the React Native CLI in order to make development easier. You should re-enable ATS prior to building your app for production by removing the <code>NSAllowsArbitraryLoads</code> entry from your <code>Info.plist</code> file in the <code>ios/</code> folder.</p><p>To learn more about how to configure ATS on your own Xcode projects, see <a href="http://ste.vn/2015/06/10/configuring-app-transport-security-ios-9-osx-10-11/" target="_blank">this post on ATS</a>.</p><span><script>
+</span><h2><a class="anchor" name="building-your-app-for-production"></a>Building your app for production <a class="hash-link" href="docs/running-on-device.html#building-your-app-for-production">#</a></h2><p>You have built a great app using React Native, and you are now itching to release it in the App Store. The process is the same as any other native iOS app, with some additional considerations to take into account.</p><p>Building an app for distribution in the App Store requires using the <code>Release</code> scheme in Xcode. To do this, go to <strong>Product</strong> → <strong>Scheme</strong> → <strong>Edit Scheme (cmd + &lt;)</strong>, make sure you&#x27;re in the <strong>Run</strong> tab from the side, and set the Build Configuration dropdown to <code>Release</code>.</p><p>Apps built for <code>Release</code> will automatically disable the in-app Developer menu, which will prevent your users from inadvertently accessing the menu in production. It will also load the JavaScript locally, so you can put the app on a device and test whilst not connected to the computer.</p><blockquote><p>Hint</p><p>You can also use the <code>React Native CLI</code> to perform this operation using the option <code>--configuration</code> with the value <code>Release</code> (e.g. <code>react-native run-ios --configuration Release</code>).</p></blockquote><p>Once built for release, you&#x27;ll be able to distribute the app to beta testers and submit the app to the App Store.</p><h3><a class="anchor" name="app-transport-security"></a>App Transport Security <a class="hash-link" href="docs/running-on-device.html#app-transport-security">#</a></h3><p>App Transport Security is a security feature, added in iOS 9, that rejects all HTTP requests that are not sent over HTTPS. This can result in HTTP traffic being blocked, including the developer React Native server.</p><p>ATS is disabled by default in projects generated using the React Native CLI in order to make development easier. You should re-enable ATS prior to building your app for production by removing the <code>NSAllowsArbitraryLoads</code> entry from your <code>Info.plist</code> file in the <code>ios/</code> folder.</p><p>To learn more about how to configure ATS on your own Xcode projects, see <a href="http://ste.vn/2015/06/10/configuring-app-transport-security-ios-9-osx-10-11/" target="_blank">this post on ATS</a>.</p><span><script>
 // Convert <div>...<span><block /></span>...</div>
 // Into <div>...<block />...</div>
 var blocks = document.getElementsByTagName('block');