Automatic setup vs Automatic setup with CocoaPods

[pierregoutheraud]

Hi,

If I understand well, we should follow either Automatic setup or Automatic setup with CocoaPods.

The thing is that the react-native link command from Automatic setup automatically ads pod 'RNI18n', :path => '../node_modules/react-native-i18n to my Podfile. Then if I try to Pod install (later on another package install for example) the metro bundler can not build anymore.

So... If I use react-native link and then remove pod 'RNI18n', :path => '../node_modules/react-native-i18n from my Podfile the package is working great but I have a warning in the console react-native-i18n module is not correctly linked.

What am I doing wrong ?

[vinsonxing]

same issue

[hawaiishinji]

same issue

Loading dependency graph...(node:33633) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: jest-haste-map: @providesModule naming collision: Duplicate module name: react-native Paths: /Users/hawa11/workspace/test/daigou/ios/Pods/React/package.json collides with /Users/hawa11/workspace/test/daigou/node_modules/react-native/package.json

Is it correct that the pod install the whole React (actually it's react-native inside the folder)?