update website

docs/troubleshooting.html

@@ -7,7 +7,12 @@
 </span> <span class="token comment" spellcheck="true"> // iOS device are on the same Wi-Fi network.
 </span>  jsCodeLocation <span class="token operator">=</span> <span class="token punctuation">[</span>NSURL URLWithString<span class="token punctuation">:</span>@<span class="token string">&quot;http://localhost:9381/index.ios.bundle&quot;</span><span class="token punctuation">]</span><span class="token punctuation">;</span></div><h2><a class="anchor" name="watchman-took-too-long-to-load"></a>Watchman took too long to load <a class="hash-link" href="#watchman-took-too-long-to-load">#</a></h2><p>Permission settings prevent Watchman from loading. A recent update solves this, get a HEAD install of Watchman if you are experiencing this error.</p><div class="prism language-javascript">brew uninstall watchman
 brew install <span class="token operator">--</span>HEAD watchman</div><h2><a class="anchor" name="npm-locking-error"></a>NPM locking error <a class="hash-link" href="#npm-locking-error">#</a></h2><p>If in the <code>react-native init &lt;project&gt;</code> phase you saw npm fail with &quot;npm WARN locking Error: EACCES&quot; then try the following:</p><div class="prism language-javascript">sudo chown <span class="token operator">-</span>R $USER <span class="token operator">~</span><span class="token operator">/</span><span class="token punctuation">.</span>npm
-sudo chown <span class="token operator">-</span>R $USER <span class="token operator">/</span>usr<span class="token operator">/</span>local<span class="token operator">/</span>lib<span class="token operator">/</span>node_modules</div><h2><a class="anchor" name="debugging-in-chrome-hangs-and-or-does-not-work-well"></a>Debugging in Chrome hangs and/or does not work well <a class="hash-link" href="#debugging-in-chrome-hangs-and-or-does-not-work-well">#</a></h2><p>It is possible that one of your Chrome extensions is interacting in unexpected ways with the debugger. If you are having this issue, try disabling all of your extensions and re-enabling them one-by-one until you find the problematic extension.</p></div><div class="docs-prevnext"></div></div></section><footer class="wrap"><div class="right">© 2015 Facebook Inc.</div></footer></div><div id="fb-root"></div><script>
+sudo chown <span class="token operator">-</span>R $USER <span class="token operator">/</span>usr<span class="token operator">/</span>local<span class="token operator">/</span>lib<span class="token operator">/</span>node_modules</div><h2><a class="anchor" name="debugging-in-chrome-hangs-and-or-does-not-work-well"></a>Debugging in Chrome hangs and/or does not work well <a class="hash-link" href="#debugging-in-chrome-hangs-and-or-does-not-work-well">#</a></h2><p>It is possible that one of your Chrome extensions is interacting in unexpected ways with the debugger. If you are having this issue, try disabling all of your extensions and re-enabling them one-by-one until you find the problematic extension.</p><h2><a class="anchor" name="xcode-build-failures"></a>Xcode Build Failures <a class="hash-link" href="#xcode-build-failures">#</a></h2><p>To see the exact error that is causing your build to fail, go into the Issues Navigator in the left sidebar.</p><h5><a class="anchor" name="react-libraries-missing"></a>React libraries missing <a class="hash-link" href="#react-libraries-missing">#</a></h5><p>If you are using CocoaPods, verify that you have added React along with the subspecs to the <code>Podfile</code>. For example, if you were using the <code>&lt;Text /&gt;</code>, <code>&lt;Image /&gt;</code> and <code>fetch()</code> APIs, you would need to add these in your <code>Podfile</code>:</p><div class="prism language-javascript">pod <span class="token string">&#x27;React&#x27;</span><span class="token punctuation">,</span> <span class="token punctuation">:</span>subspecs <span class="token operator">=</span><span class="token operator">&gt;</span> <span class="token punctuation">[</span>
+  <span class="token string">&#x27;RCTText&#x27;</span><span class="token punctuation">,</span>
+  <span class="token string">&#x27;RCTImage&#x27;</span><span class="token punctuation">,</span>
+  <span class="token string">&#x27;RCTNetwork&#x27;</span><span class="token punctuation">,</span>
+  <span class="token string">&#x27;RCTWebSocket&#x27;</span><span class="token punctuation">,</span>
+<span class="token punctuation">]</span></div><p>Next, make sure you have run <code>pod install</code> and that a <code>Pods/</code> directory has been created in your project with React installed. CocoaPods will instruct you to use the generated <code>.xcworkspace</code> file henceforth to be able to use these installed dependencies.</p><p>If you are adding React manually, make sure you have included all the relevant dependencies, like <code>RCTText.xcodeproj</code>, <code>RCTImage.xcodeproj</code> depending on the ones you are using. Next, the binaries built by these dependencies have to be linked to your app binary. Use the <code>Linked Frameworks and Binaries</code> section in the Xcode project settings. More detailed steps are here: <a href="https://facebook.github.io/react-native/docs/linking-libraries.html#content" target="_blank">Linking Libraries</a>.</p><h5><a class="anchor" name="argument-list-too-long-recursive-header-expansion-failed"></a>Argument list too long: recursive header expansion failed <a class="hash-link" href="#argument-list-too-long-recursive-header-expansion-failed">#</a></h5><p>In the project&#x27;s build settings, <code>User Search Header Paths</code> and <code>Header Search Paths</code> are two configs that specify where Xcode should look for <code>#import</code> header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.</p><p>To revert the <code>User Search Header Paths</code> and <code>Header Search Paths</code> build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.</p></div><div class="docs-prevnext"></div></div></section><footer class="wrap"><div class="right">© 2015 Facebook Inc.</div></footer></div><div id="fb-root"></div><script>
             (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
             (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
             m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)