Closed patrick-samy closed 3 years ago
My workaround for now is to checkout master on this repo, change the .podspec
file to reflect new versions, and reference the local path for the pod in my Podfile
.
Disclaimer: I'm not entirely sure that Firebase is receiving analytics yet with this fix.
Podfile
pod 'Segment-Firebase', :path => "../node_modules/@segment/analytics-react-native-firebase/segment-firebase"
Segment-Firebase.podspec
26 s.dependency 'Analytics'
27 s.dependency 'Firebase/Core', '~> 7.1'
28 s.dependency 'FirebaseAnalytics','~> 7.1'
@patrick-samy please upgrade to analytics-react-native 1.4.4
. If the issue persists, please feel free to report your issue on that repository and i'll take a closer look. Currently, the analytics-react-native
library compiles and generates all of the React Native Destinations, so it will help to keep things organized there. Thanks!
Hello,
After updating my
react-native-firebase
packages to the latest version to fix a crash on iOS 14.2 detected by the Apple review team, it seems like I now have a conflict in dependencies.Running
pod install
leads to a conflict and I've tried cleaning upnode_modules
,Podfile.lock
and thePods
directory as well as every other solution I found on previous issues that were similar without success.Any ideas how to override the
Analytics
andnanopb
versions in theAnalytics
pods and its dependencies to reflect newer versions?package.json
Podfile