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

Loading dependency graph, done - Hangs on Windows 7 in the Company Network #13684

Closed
Manuel83 opened this issue Apr 27, 2017 · 32 comments
Closed
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@Manuel83
Copy link

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
@hongxuan229
Copy link

same here

@nicoszerman
Copy link

nicoszerman commented Jun 26, 2017

Same on Ubuntu 16.04

@semiautomatix
Copy link

Windows 10

@pedromazala
Copy link

Some news about this?

@rogerpinho
Copy link

1+

@pedromazala
Copy link

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

@lihue
Copy link

lihue commented Jul 13, 2017

Same problem on macOS Sierra

@lihue
Copy link

lihue commented Jul 14, 2017

This helped me:

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

@enguerranws
Copy link

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.

@henrynw
Copy link

henrynw commented Aug 9, 2017

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.

@yuchao-git
Copy link

Window10

@skinnyindonesian24
Copy link

same problem on OSX

@TrLam
Copy link

TrLam commented Sep 25, 2017

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

@lmiller1990
Copy link

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.

@ddobby94
Copy link

ddobby94 commented Oct 22, 2017

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.

@jonathanadler
Copy link

jonathanadler commented Oct 25, 2017

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.

@ddobby94
Copy link

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

@stale
Copy link

stale bot commented Dec 24, 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 Dec 24, 2017
@stale stale bot closed this as completed Dec 31, 2017
@paramadeep
Copy link

paramadeep commented Jan 11, 2018

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.

@itsmrTech
Copy link

+1

@eduardomacetas
Copy link

I have the same problem...

@ballenwillis
Copy link

Same problem on Ubuntu 17.10

@0xlyro
Copy link

0xlyro commented Jan 19, 2018

Same here Windows 10 any suggestion!

@Johncy1997
Copy link

same problem on ubuntu 16.04

@mehulmpt
Copy link

Same problem MacOS 10.13.2

@ecdundar
Copy link

Same Problem on "Windows 10" +1

@thedanielvogelsang
Copy link

Same

@0xlyro
Copy link

0xlyro commented Feb 8, 2018

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

@MJparis
Copy link

MJparis commented Feb 12, 2018

Same... (Windows 10)

@amtBurgos
Copy link

Same issue

@saravanakumargn
Copy link

saravanakumargn commented Apr 8, 2018

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

@ismuk
Copy link

ismuk commented Apr 9, 2018

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.

@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