Trying to update from Firebase 6.3.0 to 6.4.0- encountering this error:
[!] CocoaPods could not find compatible versions for pod "FirebaseStorage":
In Podfile:
Firebase/Storage (~> 6.4.0) was resolved to 6.4.0, which depends on
FirebaseStorage (~> 3.3.0)
FirebaseUI/Storage (~> 8.0.2) was resolved to 8.0.2, which depends on
FirebaseStorage (~> 3.2.0)
pod updateMy full Podfile
```
platform :ios, '11.1'
target 'foobar' do
# Comment the next line if you're not using Swift and don't want to use dynamic frameworks
use_frameworks!
pod 'Firebase/Core', '~> 6.4.0'
pod 'Firebase/AdMob', '~> 6.4.0'
pod 'Firebase/Auth', '~> 6.4.0'
pod 'Firebase/Firestore', '~> 6.4.0'
pod 'Firebase/Functions', '~> 6.4.0'
pod 'Firebase/Performance', '~> 6.4.0'
pod 'Firebase/RemoteConfig', '~> 6.4.0'
pod 'Firebase/Storage', '~> 6.4.0'
pod 'FirebaseUI/Storage', '~> 8.0.2'
pod 'Fabric', '~> 1.10.2'
pod 'Crashlytics', '~> 3.13.3'
pod 'Branch', '~> 0.27.1'
target 'foobarTests' do
inherit! :search_paths
# Pods for testing
end
target 'foobarUITests' do
inherit! :search_paths
# Pods for testing
end
end
```
Just waiting for the podspec to be updated. Cannot use Firebase 6.4.0 until FirebaseUI updates their Storage dependency to 3.3
Unusual, this should be updated by now. Is this reproducible in a project without FirebaseUI?
Firebase/Storage 6.4.0 incremented its FirebaseStorage requirement from 3.2 to 3.3. I can install no problem without FirebaseUI, but the podspec for FirebaseUI/Storage still requires 3.2- so the install fails. The FirebaseUI podfile doesn't specify this version requirement- only the podspec as I linked above.
I may be mistaken but I'm guessing FirebaseUI will need to publish a new version that increments the FirebaseStorage version in the podspec. I'm not a Cocoapods expert but I believe that the dependency versions are locked to each published podspec, so a new version would need to be published to update the dependency requirement.
Hey @morganchen12 we're about to ship a project and we were going to update to 6.4.0 if possible. Is this something you think will be resolved in the next couple days, or should we just stick with 6.3.0? Thanks.
I'll have a fix pushed for this on Monday.
Release is out. Thanks for filing!
Most helpful comment
Release is out. Thanks for filing!