Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[packager] Hangs on: index.ios.js [development, non-minified, hmr disabled] 0% #15332

Closed
dluksza opened this issue Aug 2, 2017 · 13 comments
Closed
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@dluksza
Copy link

dluksza commented Aug 2, 2017

Is this a bug report?

Yes

Have you read the Bugs section of the How to Contribute guide?

Yes

Environment

  1. react-native -v:
    react-native-cli: 2.0.1
    react-native: 0.47.0
  2. node -v:
    v8.2.1
  3. npm -v:
    5.3.0
  4. yarn --version:
    0.27.5

Then, specify:

  • Target Platform: iOS, Android
  • Development Operating System: macOS
  • Build tools: xcode, android studio.

Steps to Reproduce

(Write your steps here:)

  1. Start new project with react-native init BuildHangs
  2. Run react-native run-ios within BuildHangs directory
  3. Wait for ever for packager to build index.ios.js file.

Expected Behavior

Initial react-native application should start on iphone emulator.

(Write what you thought would happen.)

Actual Behavior

Nothing happen, it seams like index.ios.js file is not compiled, compilation process hangs (or exit). Packager hangs with output:

Loading dependency graph...
Bundling `index.ios.js`  [development, non-minified, hmr disabled]  ░░░░░░░░░░░░░░░░  0.0% (0/1)

(Write what happened. Add screenshots!)

Everything was working fine until today afternoon when it immediately stopped working. Probably brew update && brew upgrade has updated /something/ and react-native got broken.

Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

@nonewcode
Copy link

+1

2017-08-02 22:22:12.250 [warn][tid:main][RCTBridge.m:114] Class RCTCxxModule was not exported. Did you forget to use RCT_EXPORT_MODULE()?

@prakashsejwani
Copy link

prakashsejwani commented Aug 2, 2017

+1

I think its watchman issue which is upgrade via brew, when i uninstall watchman, its working

@nonewcode
Copy link

Can confirm @prakashsejwani. Uninstalling watchman brew uninstall watchman got this working again for me as well.

@dluksza
Copy link
Author

dluksza commented Aug 2, 2017

Uninstalling watchman fixed this issue for react demo app, but in my main project I'm facing issue described in #910

@fungilation
Copy link

fungilation commented Aug 2, 2017

Not sure if related, but regarding watchman my Packager console has this output on RN 0.47.0:

React packager ready.

Loading dependency graph.../Users/<user>/Library/LaunchAgents/com.github.facebook.watchman.plist: Could not find specified service

Loading dependency graph, done.
Bundling `index.ios.js`  [development, non-minified, hmr disabled]  ░░░░░░░░░░░░░░░░  0.0% (0/1)Launching Dev Tools...
Bundling `index.ios.js`  [development, non-minified, hmr disabled]  100.0% (599/599), done.

EDIT: the "watchman.plist: Could not find specified service" line no longer appears on run-ios, on RN 0.47.1

@dluksza
Copy link
Author

dluksza commented Aug 2, 2017

Running launchctl unload -F $HOME/Library/LaunchAgents/com.github.facebook.watchman.plist fix both issues for me. Now I'm able to run react-native with watchman again :)

Thanks to @danielfarrell for figuring this out on facebook/watchman#511 (comment)

@youmyyou
Copy link

youmyyou commented Aug 3, 2017

@dluksza how to open hmr?

@dluksza
Copy link
Author

dluksza commented Aug 3, 2017

@youmyyou I don't know how to open hmr, never did that and never was interested in opening it

@prank7
Copy link

prank7 commented Aug 11, 2017

@youmyyou did you figure out how to open hmr?

@olviejs
Copy link

olviejs commented Aug 15, 2017

@JoshuaKelly work for me, tks.

@faizmokh
Copy link

I'm currently experiencing the same issue too right now. Uninstalling watchman only worked the first time. Running launchctl unload -F $HOME/Library/LaunchAgents/com.github.facebook.watchman.plist also doesn't work.

@iMokhles
Copy link

#15671 i fixed this issue and posted my fix hope It helps you

@stale
Copy link

stale bot commented Oct 26, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Oct 26, 2017
@stale stale bot closed this as completed Nov 2, 2017
@facebook facebook locked and limited conversation to collaborators May 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests

9 participants