Doubled packager for start:ios & start:android?

Hey team,

Every time I run either yarn start:android or yarn start:ios I get two packager launched:

The line being executed is: concurrently -r 'react-native start' 'react-native run-android' It seems to me that react-native run-X starts its own packager, so we don’t really need to concurrently react-native start

It’s been the case since I started contributing on GitPoint, and since no one complained about so far, I’m wondering if you guys are also experiencing this, or if it’s only affecting me… 🤔

[machour]

@chinesedfan no problems at all. Added some console.log() statement in both files, here’s what’s happening:

As you can see, the fetch() completed quickly with “not_running”, so runAndroid starts a new one. (the one it starts is opened in the white window). Immediately after this first test fails, the packager supposed to be started by “react-native start” is finally up & running, so the new packager fails.

If I add for (var i = 0; i < 10000000000000; i++) {} in runAndroid before the isPackagerReady() test is executed, the double popup disappears. This is because by the time the fetch() is done, our first packager is already up and running.

[chinesedfan]

@machour I don’t think it has relationship with global react-native. My global react-native is linked to a strange place. Let’s talk in gitter. 😃

[zhong@localhost git-point]$ react-native --version
Looks like you installed react-native globally, maybe you meant react-native-cli?
To fix the issue, run:
npm uninstall -g react-native
npm install -g react-native-cli
[zhong@localhost git-point]$ ll `which react-native`
lrwxr-xr-x  1 zhong  admin  98  9  6 22:32 /usr/local/bin/react-native -> ../../../Users/zhong/.config/yarn/global/node_modules/react-native/local-cli/wrong-react-native.js