React-native: Loading dependency graph, done - Hangs on Windows 7 in the Company Network

Created on 27 Apr 2017  路  32Comments  路  Source: facebook/react-native

Description

I try to setup a ReactNative Project on Windows 7 with Andorid Emulator in the company network.
I run "react-native start" but it seems to hang. I waited for 10 min without progress. Our company network requires to set a proxy. Is build process connecting to the internet? If yes how can I set a proxy server for this step? Is there any way to debug this step to see what's going on?

image

image

Reproduction Steps and Sample Code

Solution

Additional Information

  • React Native version: 0.43.4
  • Platform: Andorid
  • Development Operating System: Windows 7
  • Dev tools: Android Studio 2.3.1
Stale

Most helpful comment

Windows 10

All 32 comments

same here

Same on Ubuntu 16.04

Windows 10

Some news about this?

1+

People, I removed all dependencies on Expo, and then I added all again. Afetr run yarn install my app get back to life.

Same problem on macOS Sierra

This helped me:

  • delete node_modules folder
  • npm install
  • npm run ios (or react-native run-ios)

Here's how I deal with it (dumb way): just stop the packager session in your terminal and react-native run-ios again (and again if it still not work).

Some information about what's going on would be appreciated.

For me, I fixed it by making sure I had these settings in Xcode Info.plist:

  • App Transport Security Settings:

    • Exception Domains



      • localhost (Dictionary)


      • NSTemporaryExceptionAllowsInsecureHTTPLoads (Boolean: YES)



After that, I rerun react-native run-ios and then it continues past the "Loading dependency graph, done". message.

Window10

same problem on OSX

My fix was adding the FORCE_BUNDLING flag while building.
So: react-native run-ios FORCE_BUNDLING
It continues bundling after the "Loading dependency graph, done." message

Mid way through development I hit this problem. I had run nvm use 8 which set my node version to 8.4. I run nvm use 7 to use 7.2.1, and it worked fine. So if you are on node 8, try <7.

I am still getting this error.
Brand new ignite installed + generated some screens & containers with ignite cmd commands, with every needed library on win 10.
Downgraded npm to v6, nothing.
Deleted & reinstalled all node_modules, did not work.

Although, the react-native run-android command builds & installs the debug.apk on my device.

After rm -rf node_modules && npm install didn't help me, I uninstalled the app from the simulator, and ran it again, and the problem was fixed.

I'm using xcode on osx, with npm 6.10.

I kind of solved the error.
Delete everything and generate new app with ignite from scratch worked for me.

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.

I tried all the above suggestions, I'm having the latest version a node, and using latest version on react-native. any help is much appreciated. I am facing the issue in mac.

+1

I have the same problem...

Same problem on Ubuntu 17.10

Same here Windows 10 any suggestion!

same problem on ubuntu 16.04

Same problem MacOS 10.13.2

Same Problem on "Windows 10" +1

Same

update: I managed to run this on my MacOS 10.13 although I've been thru some identical problems like Windows but the last thing was to uninstall Java 9 and install Java 8 using brew cask java 8.

Setting up your development environment can be somewhat tedious

Same... (Windows 10)

Same issue

Make sure in Wifi is Turned on in Android & iOS emulator

Same issues windows 10 - my solution, in case it helps anyone: I am using Webstorm as IDE and using the inbuilt terminal to run npm start android. Works fine until after a shutdown and reboot and then hangs as previously described. To get it working again I need to close and then reopen the inbuilt terminal window.

Was this page helpful?
0 / 5 - 0 ratings