React-native-firebase: 馃敟 "Unable to find a specification for `RNFBApp` depended upon by `RNFBAnalytics`"

Created on 16 Oct 2019  路  7Comments  路  Source: invertase/react-native-firebase

Issue

Getting when trying to upgrade from 0.2.3 to 0.6.1. I updated the dependencies in my package.json and ran the following commands
React Native 0.60.5

rm -rf ./node_modules && yarn install
rm -r ~/Library/Developer/Xcode/DerivedData
cd ./ios && pod deintegrate && pod repo update && pod install ; cd ..

and I get the following error

[!] Unable to find a specification for `RNFBApp` depended upon by `RNFBAnalytics`

You have either:
 * out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`.
 * mistyped the name or version.
 * not added the source repo that hosts the Podspec to your Podfile.

Click To Expand

**`pod install --repo-update` output:**

Detected React Native module pods for {...}, RNFBAnalytics, RNFBPerf, {...}
Updating local specs repositories
Analyzing dependencies
Fetching podspec for `DoubleConversion` from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`
Fetching podspec for `Folly` from `../node_modules/react-native/third-party-podspecs/Folly.podspec`
Fetching podspec for `glog` from `../node_modules/react-native/third-party-podspecs/glog.podspec`
[!] Unable to find a specification for `RNFBApp` depended upon by `RNFBAnalytics`

You have either:
 * mistyped the name or version.
 * not added the source repo that hosts the Podspec to your Podfile.

I also tried adding
"@react-native-community/cli": "^2.9.0", as per https://github.com/invertase/react-native-firebase/issues/2668 to no avail.

Also, when running react-native start I get

warn Package @react-native-firebase/app has been ignored because it contains invalid configuration. Reason: Unknown option dependency.platforms.ios.scriptPhases with value "[{"name":"[RNFB] Core Configuration","path":"./ios_config.sh","execution_position":"after_compile"}]" was found. This is either a typing error or a user mistake. Fixing it will remove this message.
warn Package @react-native-firebase/crashlytics has been ignored because it contains invalid configuration. Reason: Unknown option dependency.platforms.ios.scriptPhases with value "[{"name":"[RNFB] Crashlytics Configuration","path":"./ios_config.sh","execution_position":"after_compile"}]" was found. This is either a typing error or a user mistake. Fixing it will remove this message.

Project Files

iOS

  • [ ] I'm not using Pods
  • [x] I'm using Pods and my Podfile looks like:
platform :ios, '10.0'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
project '{project_name}.xcodeproj'

target '{project_name}' do
    pod 'React', :path => '../node_modules/react-native/'
    pod 'React-Core', :path => '../node_modules/react-native/React'
    pod 'React-DevSupport', :path => '../node_modules/react-native/React'
    pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
    pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
    pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
    pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
    pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
    pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
    pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
    pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
    pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
    pod 'React-RCTWebSocket', :path => '../node_modules/react-native/Libraries/WebSocket'

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

    pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
    pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
    pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'

    target '{project_name}Tests' do
        # Pods for testing
    end

    use_native_modules!
end

Android

N/A

Environment

Click To Expand

**`react-native info` output:**

System:
    OS: macOS 10.15
    CPU: (8) x64 Intel(R) Core(TM) i7-7920HQ CPU @ 3.10GHz
    Memory: 518.60 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.9.1 - /usr/local/bin/node
    Yarn: 1.17.3 - /usr/local/bin/yarn
    npm: 6.10.3 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.1, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
    Android SDK:
      API Levels: 23, 26, 27, 28
      Build Tools: 23.0.1, 27.0.3, 28.0.0, 28.0.2, 28.0.3
      System Images: android-26 | Google APIs Intel x86 Atom_64, android-27 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom_64
  IDEs:
    Android Studio: 3.5 AI-191.8026.42.35.5791312
    Xcode: 11.1/11A1027 - /usr/bin/xcodebuild
  npmPackages:
    @react-native-community/cli: ^2.9.0 => 2.9.0
    react: 16.8.6 => 16.8.6
    react-native: 0.60.5 => 0.60.5
  npmGlobalPackages:
    react-native-cli: 2.0.1
    react-native-git-upgrade: 0.2.7
- **Platform that you're experiencing the issue on**: - [x] iOS - [ ] Android - [ ] **iOS** but have not tested behavior on Android - [ ] **Android** but have not tested behavior on iOS - [ ] Both - **`react-native-firebase` version you're using that has this issue:** - 6.0.1 - **`Firebase` module(s) you're using that has the issue:**
"@react-native-firebase/analytics": "^6.0.1",
"@react-native-firebase/app": "^6.0.1",
"@react-native-firebase/crashlytics": "^6.0.1",
"@react-native-firebase/perf": "^6.0.1",
- **Are you using `TypeScript`?** - `Y`

Stale

Most helpful comment

I've also encountered this issue today when upgrading from 0.3.0 to 6.0.2. I found from the pod install logs that the RNFBApp pod was missing, so it had not been auto-linked correctly.

I didn't find why that pod is no longer auto-linking, but adding the following to my Podfile to manually link the library resolved my issue:

pod 'RNFBApp', :path => '../node_modules/@react-native-firebase/app'

All 7 comments

I've also encountered this issue today when upgrading from 0.3.0 to 6.0.2. I found from the pod install logs that the RNFBApp pod was missing, so it had not been auto-linked correctly.

I didn't find why that pod is no longer auto-linking, but adding the following to my Podfile to manually link the library resolved my issue:

pod 'RNFBApp', :path => '../node_modules/@react-native-firebase/app'

Same issue

Also having this issue

Still getting the warning for iOS.

These warnings:

warn Package @react-native-firebase/app has been ignored because it contains invalid configuration. Reason: Unknown option dependency.platforms.ios.scriptPhases with value "[{"name":"[RNFB] Core Configuration","path":"./ios_config.sh","execution_position":"after_compile"}]" was found. This is either a typing error or a user mistake. Fixing it will remove this message.

They're 100% a local CLI issue using an older version. The chances are you've got the old (pre community) CLI installed which is being used on install. I'd go into your global node_modules directory and remove the old version completely.

Hello 馃憢, to help manage issues we automatically close stale issues.
This issue has been automatically marked as stale because it has not had activity for quite some time. Has this issue been fixed, or does it still require the community's attention?

This issue will be closed in 15 days if no further activity occurs.
Thank you for your contributions.

Closing this issue after a prolonged period of inactivity. If this is still present in the latest release, please feel free to create a new issue with up-to-date information.

Was this page helpful?
0 / 5 - 0 ratings