Add troubleshooting and modification for linux
Summary: Thanks for submitting a pull request! Please provide enough information so that others can review your pull request: (You can skip this if you're fixing a typo or adding an app to the Showcase.) Explain the **motivation** for making this change. What existing problem does the pull request solve? Prefer **small pull requests**. These are much easier to review and more likely to get merged. Make sure the PR does only one thing, otherwise please split it. **Test plan (required)** Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI. Make sure tests pass on both Travis and Circle CI. **Code formatting** Look around. Match the style of the rest of the codebase. See also the simple [style guide](https://github.com/facebook/react-native/blob/master/CONTRIBUTING.md#style-guide). For more info, see the ["Pull Requests" section of our "Contributing" guidelines](https://github.com/facebook/react-native/blob/mas Closes https://github.com/facebook/react-native/pull/7471 Differential Revision: D3276360 Pulled By: JoelMarcey fb-gh-sync-id: 30edd7086a3c4b88695dc91af76ef56d43306ce9 fbshipit-source-id: 30edd7086a3c4b88695dc91af76ef56d43306ce9
This commit is contained in:
parent
146df61775
commit
e737891242
|
@ -713,11 +713,11 @@ cd AwesomeProject
|
|||
react-native run-android
|
||||
```
|
||||
|
||||
<block class="windows android" />
|
||||
<block class="windows linux android" />
|
||||
|
||||
### Troubleshooting Run
|
||||
|
||||
A common issue on Windows is that the packager is not started automatically when you run
|
||||
A common issue is that the packager is not started automatically when you run
|
||||
`react-native run-android`. You can start it manually using:
|
||||
|
||||
```
|
||||
|
@ -725,13 +725,18 @@ cd AwesomeProject
|
|||
react-native start
|
||||
```
|
||||
|
||||
<block class="windows android" />
|
||||
|
||||
Or if you hit a `ERROR Watcher took too long to load` on Windows, try increasing the timeout in [this file](https://github.com/facebook/react-native/blob/5fa33f3d07f8595a188f6fe04d6168a6ede1e721/packager/react-packager/src/DependencyResolver/FileWatcher/index.js#L16) (under your `node_modules/react-native/`).
|
||||
|
||||
<block class="windows linux android" />
|
||||
|
||||
### Modifying Project
|
||||
|
||||
Now that you successfully started the project, let's modify it:
|
||||
|
||||
- Press the `R` key twice **OR** open the menu (F2 by default, or ⌘-M in Genymotion) and select Reload JS to see your change!
|
||||
- Open `index.android.js` in your text editor of choice (e.g. [Nuclide](http://nuclide.io/docs/platforms/react-native/)) and edit some lines.
|
||||
- Press the `R` key twice **OR** open the menu (F2 by default, or ⌘-M in the emulator) and select Reload JS to see your change!
|
||||
- Run `adb logcat *:S ReactNative:V ReactNativeJS:V` in a terminal to see your app's logs
|
||||
|
||||
### That's It
|
||||
|
|
Loading…
Reference in New Issue