firebase-ios-sdk: Unable to install the Firebase iOS SDK (7.9.0) through SPM

Environment

  • Xcode version: 12.4
  • Firebase SDK version: 7.9.0
  • Installation method: Swift Package Manager
  • Firebase Component: Take your pick… I could not get the option to select the desired components.

Problem

Unable to install the Firebase iOS SDK (7.9.0) through SPM. Failing with the error: Failed to resolve dependencies

This seems to be a problem isolated to 7.9.0, I am able to install 7.8.1 with no issues. I tried using different targeted iOS versions ranging from 13.0 - 14.4.

Reseting the Package Cache had no effect.

Failed to resolve dependencies because no versions of firebase-ios-sdk match the requirement 7.9.1..<8.0.0 and package firebase-ios-sdk is required using a version-based requirement and it depends on unversion package grpc-swiftpm, firebase-ios-sdk >=7.9.0 is forbidden.
And because root depends on firebase-ios-sdk 7.9.0..<8.0.0, version solving failed.

Steps to reproduce:

  1. Create a new project in Xcode.
  2. Add “https://github.com/firebase/firebase-ios-sdk.git” as a Package Dependency with the exact version of 7.9.0.

Thanks for taking the time! I’m glad to see Firebase SwiftUI support extending through the new FirebaseAnalyticsSwift component as well. 😃

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 2
  • Comments: 18 (9 by maintainers)

Most upvoted comments

@paulb777 I think what did it to me was to reset the package cache. I also run the Swift Packages -> Update to Latest Package Versions but well, seems to works, thanks a lot and sorry to make noise on the thread, it was driving me crazy all day. Thanks again

@paulb777 abseil 0.20200225.2 seems to have done the trick. I don’t think 7.9.2 is required. Thanks again

I just published a 7.9.1 and verified that my test example is fixed with that.

For future reference, I first tried moving the 7.9.0 tag, but Xcode used a cached version of the repo and tag that didn’t get reset even after removing DerivedData.

@cpdunphy Thanks for the report. I’ve reproduced and we’re investigating …