-
Notifications
You must be signed in to change notification settings - Fork 335
"Loading dependency graph, done" #51
Comments
also tried:
as per this github issue also tried: Running |
|
@dillon Did you manage to fix it? I'm having the same issue on Android EDIT: Fixed it for android by following this: https://stackoverflow.com/questions/52111298/how-to-solve-app-launch-app-is-stuck-on-white-screen?noredirect=1 |
@JacekRojek no I haven’t been able to fix it |
This is still an issue for me |
I'm having this problem too. I can start a new project as per the instructions and I get this:
Then it hangs forever. Creating an app using create-react-native-app works fine, so this seems like a bug with react-native-firebase-starter. |
Please try the latest changes on master, thanks 👍 Loving
|
So I have a similar issue when I follow this https://rnfirebase.io/docs/v5.x.x/installation/ios, anyone here still running into this issue? |
i have found the perfect solution for it use command prompt to run the react-native start, let it be stuck on dependency graph then run react-native run-android on your ide terminal works for me |
Environment
macOS High Sierra 10.13.6
Xcode 9.4.1
React Native
version:react-native-cli: 2.0.1
react-native: 0.55.4
React Native Firebase
Version:"react-native-firebase": "^4.3.6",
Firebase
Module:auth, database
typescript
?no
My project can never get past
Loading dependency graph, done.
I rolled back to a previous version when it was working and reinstalled node_moduels with yarn, but it didn't help.
So I then tried starting from scratch, but the same happens with a completely blank
react-native-firebase-starter
(into which I imported my previous firebase project's credentials).Note that it works fine when using a blank
create-react-native-app
appTerminal shows the following output indefinitely (I've waited for up to 40 minutes):
...
...
The simulator never opens. If I try opening the simulator first and then running
yarn start
, the simulator doesn't change at all (or even open expo). Opening expo manually doesn't do anything either.This has happened once before, and I managed to fix it. I believe it was from installing watchman (which I hadn't had installed globally with brew yet)
Here are the fixes I've tried so far, (mostly one at a time, and then rolling back changes):
watchman watch-del-all
after each attempt at bundlingrm -rf node_modules && yarn
react-native run-ios
(this generates a ton of new files in theios/
folder, but works initially, until I try to add an import statement of any module (evenimport firebase from 'firebase'
) in any of my js files and it throws an error on the ios simulator screen that it can't find the module. I can do this again to get that error for you if you'd like me to).react-native upgrade
/usr/local/var/run/watchman/
thenbrew reinstall the watchman
127.0.0.1 localhost
is in your/etc/hosts
file. (it already was)yarn start
Erase all content and settings
on xcode simulatorhttp://localhost:8081/index.ios.bundle
into the browser resulted in the following output in browser window:package.json:
The text was updated successfully, but these errors were encountered: