React pod has been deprecated and build fails

[samuela]

Issue

The React pod, which is one of RNFirebase's dependencies, has been deprecated. A minimal Podfile looks something like

platform :ios, '9.0'

target 'ReactNativePlayground' do
  pod 'Firebase/Core'
  pod 'RNFirebase', :path => '../node_modules/react-native-firebase'
end

and running pod update && pod install, produces a warning

[!] React has been deprecated

Environment

1. Application Target Platform: iOS

2. Development Operating System: macOS 10.12.6

3. Build Tools: N/A

4. React Native version: 0.48.3

5. RNFirebase Version: 2.2.0

6. Firebase Module: N/A

[samuela]

Addendum: this causes builds to fail with RN 0.48.3, RNFirebase 2.2.0, and pods:

  - React (0.11.0):
    - React/Core (= 0.11.0)
  - React/Core (0.11.0)

The react native packager produces

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Object.es6
  Paths: /Users/samuelainsworth/Development/ReactNativePlayground/ios/Pods/React/packager/react-packager/src/DependencyResolver/polyfills/polyfills.js collides with /Users/samuelainsworth/Development/ReactNativePlayground/node_modules/react-native/Libraries/polyfills/Object.es6.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: react-native
  Paths: /Users/samuelainsworth/Development/ReactNativePlayground/ios/Pods/React/package.json collides with /Users/samuelainsworth/Development/ReactNativePlayground/node_modules/react-native/package.json

.......

This warning is caused by a @providesModule declaration with the same name across two different files.
Bundling `index.ios.js`  [development, non-minified, hmr disabled]  0.0% (0/1), failed.
error: bundling failed: ambiguous resolution: module `/Users/samuelainsworth/Development/ReactNativePlayground/index.ios.js` tries to require `react-native`, but there are several files providing this module. You can delete or fix them: 

  * `/Users/samuelainsworth/Development/ReactNativePlayground/ios/Pods/React/package.json`
  * `/Users/samuelainsworth/Development/ReactNativePlayground/node_modules/react-native/package.json`

I'm confident that this issue is tied to the deprecation of the React pod, etc. but I cannot be entirely certain, and others' insights here would of course be appreciated.

[samuela]

Ah, so the pod deprecation warning is because I am a fool and forgot the

pod "Yoga", :path => "../node_modules/react-native/ReactCommon/yoga"
pod 'React', :path => '../node_modules/react-native', :subspecs => [
  'BatchedBridge', # Required For React Native 0.45.0+
  'Core',
  # Add any other subspecs you want to use in your project
]

section in my Podfile. However, the ambiguous resolution errors persist.

[samuela]

Further edit: I was having build issues, but I was able to resolve them by adding DevSupport to the subspecs list for React:

pod 'React', :path => '../node_modules/react-native', :subspecs => [
  'BatchedBridge', # Required For React Native 0.45.0+
  'Core',
  'DevSupport'
  # Add any other subspecs you want to use in your project
]

Now the react-native run-ios build "succeeds." However, I'm still seeing the same bundling issue:

Bundling `index.ios.js`  [development, non-minified, hmr disabled]  0.0% (0/1), failed.
error: bundling failed: ambiguous resolution: module `/Users/samuelainsworth/Development/ReactNativePlayground/index.ios.js` tries to require `react-native`, but there are several files providing this module. You can delete or fix them: 

  * `/Users/samuelainsworth/Development/ReactNativePlayground/ios/Pods/React/package.json`
  * `/Users/samuelainsworth/Development/ReactNativePlayground/node_modules/react-native/package.json`

Here's the simulator perspective:

[olivierlesnicki]

Seeing same issue as @samuela

[olivierlesnicki]

For some reason the install process also creates a React folder under /ios/Pods, deleting it fixes the issue:
microsoft/react-native-code-push#745

[samuela]

@olivierlesnicki My understanding is that the /ios/Pods/React/ folder is brought into existence because of the

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

bit in the Podfile. Are you sure it's safe to delete it?

[JackThomson2]

Hi guys I had a similar issue with you but it was to do with archiving try adding this at the bottom of your pod file:

post_install do |installer|
  installer.pods_project.targets.each do |target|
    if target.name == "React"
      target.remove_from_project
    end
  end
end

[chrisbianca]

Docs have been updated with @JackThomson2's fix above which has been confirmed to work in certain situations. Please re-open if this is still an issue.

With v3.x we are looking at getting react-native link to work again - unfortunately basic support provided by React doesn't give us the right level of customisation for Android, but we'll figure something out.

[johnernaut]

Hi, I've added the fix described by @JackThomson2 for this in my Podfile, and I've confirmed that Pods/React does not exist, but I'm still getting the following error from the react packager:

Bundling `index.ios.js`  [development, non-minified, hmr disabled]  0.0% (0/1), failed.
error: bundling failed: ambiguous resolution: module `/Users/<user>/code/RMMobile/index.ios.js` tries to require `react-native`, but there are several files providing this module. You can delete or fix them:
* `/Users/<user>/code/RMMobile/ios/Pods/React/package.json`
* `/Users/<user>/code/RMMobile/node_modules/react-native/package.json`

I've also made sure my React pod path is pointed into my node_modules directory for reference.

Any ideas?

EDIT:

I was able to resolve this issue by clearing the react packager cache.

[bramus]

Referencing software-mansion/react-native-svg#463

[staufman]

If anyone else is seeing there, it may be because the block of code in the Podfile (see the post a few above this one) which removes React was added after running pod install once. In this case, the React pod will be in your Pods/ directory and it will not be removed after running pod install. In short, try deleting your Pods/ directory and then run pod install. You will most likely need to reset your cache too i.e. npm start -- --reset-cache.