Closed Khachik98 closed 2 years ago
Your podfile looks extremely suspect, I don't think this is supportable in any way:
pod 'Firebase/Analytics'
pod 'Firebase/Core', '> 6.13.0'
pod 'Firebase/Messaging', '> 6.13.0'
pod 'GoogleIDFASupport', '~> 3.14.0'
pod 'react-native-branch', :path => '../node_modules/react-native-branch'
pod 'RNFBApp', :path => '../node_modules/@react-native-firebase/app'
pod 'RNFBCrashlytics', :path => '../node_modules/@react-native-firebase/crashlytics'
First, you are bringing in concrete versions of firebase modules. You must not do that. @react-native-firebase/app
controls the versions and if you need to override them you do so according to the documentation: https://rnfirebase.io/#ios
So you will remove the top 4 lines I quote.
We use auto-linking and do not support manual linking really, you are on your own if doing that as it indicates some deep project integration failures which make support impossible. So you should remove the last two lines I quote.
Here's a script that shows a proper integration starting from scratch: https://github.com/mikehardy/rnfbdemo/blob/main/make-demo.sh
Once you've removed at least the concrete versions for modules that should never be included in the Podfile, you will stop having Pod version mismatch issues
Your podfile looks extremely suspect, I don't think this is supportable in any way:
pod 'Firebase/Analytics' pod 'Firebase/Core', '> 6.13.0' pod 'Firebase/Messaging', '> 6.13.0' pod 'GoogleIDFASupport', '~> 3.14.0' pod 'react-native-branch', :path => '../node_modules/react-native-branch' pod 'RNFBApp', :path => '../node_modules/@react-native-firebase/app' pod 'RNFBCrashlytics', :path => '../node_modules/@react-native-firebase/crashlytics'
First, you are bringing in concrete versions of firebase modules. You must not do that.
@react-native-firebase/app
controls the versions and if you need to override them you do so according to the documentation: https://rnfirebase.io/#iosSo you will remove the top 4 lines I quote.
We use auto-linking and do not support manual linking really, you are on your own if doing that as it indicates some deep project integration failures which make support impossible. So you should remove the last two lines I quote.
Here's a script that shows a proper integration starting from scratch: https://github.com/mikehardy/rnfbdemo/blob/main/make-demo.sh
Once you've removed at least the concrete versions for modules that should never be included in the Podfile, you will stop having Pod version mismatch issues
After removing these lines when I run 'pod install' I get this error.
[!] The following Swift pods cannot yet be integrated as static libraries: The Swift pod
FirebaseCoreInternal
depends uponGoogleUtilities
, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may setuse_modular_headers!
globally in your Podfile, or specify:modular_headers => true
for particular dependencies.
Podfile.lock is deleted from me
Interesting - now I think I see why people attempting to use react-native-firebase v15 are adding use_modular_headers
everywhere, that has really been confusing to me. It's not in our guides anywhere but I'm starting to see Podfiles with that stuff scattered all over it.
As near as I can tell hermes and Flipper are still not working with use_frameworks
, so those are out.
My make-demo script still works for me (with react-native 0.69.0 - I still need to update it) and though I have hermes in there for release versions you either need to disable bitcode or disable hermes (I recommend disabling bitcode), but it works, there are no pod install failures I'm aware of
I get an error installing "crashlytics" when I run 'pod install' or 'pod install --repo-update'.
My package.json
My Podfile
My AppDelegate.m
Xcode Version 12.0