react-native: Ambiguous resolution of react-native

@ManvendraSK npm start -- --reset-cache saved the day for me: https://github.com/facebook/react-native/issues/1924#issuecomment-249861004

Also, delete system32

I’m having the same problem. It’s pointing to package.json files in directories that no longer exists. Have tried npm cache clean yarn cache clean etc… Keeps trying to resolve the react_native module to the non-existent dirs.

Any idea when this will be solved? For now I cannot install any pods that install React as well.

Reboot mac works

i tried to install, npm install --save react-native-router-flux@3.38.0 npm install -g react-native-git-upgrade react-native-git-upgrade

fixed thanks folks

@ManvendraSK try watchman watch-del-all Unfortunately, it did not help me 😞

Generally this issue arises when there are two folders of react-native. More often, if you use Pods, you have dependency that relies on the ‘React’ pod and thus you should reference the pod in your node_modules/ not install anothe react-native from cocopods. To do so, you can add the following to your Podfile

  pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
  pod 'React', :path => '../node_modules/react-native'

For me the error appeared in calling my Project ReactNative! As soon as I changed the name to something different than ./ReactNative the error disappeared!

Hey @jonathanoron and @radko93, it’s working fine!

npm start -- --reset-cache does work! But, after it has executed we need to kill this command and start with the usual one react-native run-android. watchman didn’t work though!

Thanks, guys. You both are Batman for me!

@jonathanoron I’ll try when back at home, right now in office 😉.

Let’s see what is next, I’ll keep you posted here. May be somebody would help like Batman! 😛