react-native: Code change never showing up on reload (Hot reload not working either)

Description

So I am following the sample app. This used to work on my old machine, but I moved to a new one and suddenly it’s not working.

Seems like watchman is not detecting file changes anymore?

AwesomeProject ➜ npm run start

> AwesomeProject@0.0.1 start /Users/jordan/Desktop/AwesomeProject
> node node_modules/react-native/local-cli/cli.js start

(node:372) DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
(node:372) DeprecationWarning: Using Buffer without `new` will soon stop working. Use `new Buffer()`, or preferably `Buffer.from()`, `Buffer.allocUnsafe()` or `Buffer.alloc()` instead.
Scanning 709 folders for symlinks in /Users/jordan/Desktop/AwesomeProject/node_modules (4ms)
 ┌────────────────────────────────────────────────────────────────────────────┐
 │  Running packager on port 8081.                                            │
 │                                                                            │
 │  Keep this packager running while developing on any JS projects. Feel      │
 │  free to close this tab and run your own packager instance if you          │
 │  prefer.                                                                   │
 │                                                                            │
 │  https://github.com/facebook/react-native                                  │
 │                                                                            │
 └────────────────────────────────────────────────────────────────────────────┘
Looking for JS files in
   /Users/jordan/Desktop/AwesomeProject

[Hot Module Replacement] Server listening on /hot

React packager ready.

[11/11/2016, 9:15:16 PM] <START> Initializing Packager
[11/11/2016, 9:15:16 PM] <START> Building in-memory fs for JavaScript
[11/11/2016, 9:15:16 PM] <END>   Building in-memory fs for JavaScript (193ms)
[11/11/2016, 9:15:16 PM] <START> Building Haste Map
[11/11/2016, 9:15:17 PM] <END>   Building Haste Map (600ms)
[11/11/2016, 9:15:17 PM] <END>   Initializing Packager (869ms)

I see the above when I run npm run start. If I make a change to index.ios.js and save it, nothing happens. And if I hit CMD-r the simulator reloads but my change does not appear unless I stop npm run start and run it again.

Reproduction

I just did this:

react-native init AwesomeProject
cd AwesomeProject
react-native run-ios

And then ran npm run start or even if I do react-native run-ios, same issue.

Additional Information

react-native-cli: 1.2.0 react-native: 0.37.0 node: v7.0.0 watchman: 4.7.0

  • Platform: ios and android
  • Operating System: MacOS Sierra.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 18 (2 by maintainers)

Most upvoted comments

Hey everyone. @leeight @RomualdPercereau @chanceeakin @bluefantasy728 Did some playing around and wasn’t getting answers anywhere.

I did the following and it seems to be working now:

rm -rf /usr/local/var/run/watchman && brew uninstall watchman && brew install watchman

Hopefully that works for you!

@Jonovono: It worked!!!

You’re the hero we need, not the one we deserve.

@Jonovono well It worked. I just wanted to add some Points

  1. Initially I was deleting the folder /usr/local/var/run/watchman/$USER-state which is not giving me desired result.

  2. Watchman does not detect changes in the folder where .lock file is present. There is a yarn.lock file which is generated when we are installing yarn thus we have to remove that lock file. And, no need to uninstall and install watchman in my Case.

Thank You @Jonovono

Simply restarting the packager worked for me

npm install --save-dev react-native-cli sIMPLY use this