firebase-ios-sdk: Error satisfying GoogleUtilities/MethodSwizzler dependency.

Xcode version: 10.0 (10A255)
Firebase SDK version: 5.8.0
Firebase Component: Auth, Core, Database, Functions, Messaging, Performance, Storage
Component version: 5.8.0

Steps to reproduce:

Create a new Xcode project
pod init
Add the following lines in the Podfile

pod 'Firebase'
pod 'Firebase/Auth'
pod 'Firebase/Core'
pod 'Firebase/Database'
pod 'Firebase/Functions'
pod 'Firebase/Messaging'
pod 'Firebase/Performance'
pod 'Firebase/Storage'

Note: Changing the platform to platform :ios, '12.0' causes the same issue.

pod install

Analyzing dependencies
[!] CocoaPods could not find compatible versions for pod "Firebase/Performance":
  In Podfile:
    Firebase/Performance

Specs satisfying the `Firebase/Performance` dependency were found, but they required a higher minimum deployment target.
CocoaPods could not find compatible versions for pod "GoogleUtilities/MethodSwizzler":
  In Podfile:
    Firebase/Performance was resolved to 5.8.0, which depends on
      FirebasePerformance (= 2.1.1) was resolved to 2.1.1, which depends on
        GoogleUtilities/MethodSwizzler (~> 5.2.0)

Specs satisfying the `GoogleUtilities/MethodSwizzler (~> 5.2.0)` dependency were found, but they required a higher minimum deployment target.

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 1
Comments: 35 (10 by maintainers)

Commits related to this issue

workaround for dependency failures when doing pod update https://github.com/firebase/firebase-ios-sdk/issues/1845#issuecomment-422831481 Signed-off-by: Jakub Sokołowski <jakub@status.im> — committed to status-im/status-mobile by jakubgs 6 years ago
workaround for dependency failures when doing pod update https://github.com/firebase/firebase-ios-sdk/issues/1845#issuecomment-422831481 Signed-off-by: Jakub Sokołowski <jakub@status.im> — committed to status-im/status-mobile by pombeirp 6 years ago
workaround for dependency failures when doing pod update https://github.com/firebase/firebase-ios-sdk/issues/1845#issuecomment-422831481 Signed-off-by: Jakub Sokołowski <jakub@status.im> — committed to status-im/status-mobile by jakubgs 6 years ago
workaround for dependency failures when doing pod update https://github.com/firebase/firebase-ios-sdk/issues/1845#issuecomment-422831481 Signed-off-by: Jakub Sokołowski <jakub@status.im> — committed to status-im/status-mobile by jakubgs 6 years ago
workaround for dependency failures when doing pod update https://github.com/firebase/firebase-ios-sdk/issues/1845#issuecomment-422831481 Signed-off-by: Jakub Sokołowski <jakub@status.im> — committed to status-im/status-mobile by jakubgs 6 years ago
workaround for dependency failures when doing pod update https://github.com/firebase/firebase-ios-sdk/issues/1845#issuecomment-422831481 Signed-off-by: Jakub Sokołowski <jakub@status.im> — committed to 751895405/status-react by jakubgs 6 years ago

Most upvoted comments

This looks like a CocoaPods bug with version resolution.

A workaround is adding pod 'GoogleUtilities', '5.2.3' to the Podfile.

We’ll continue to investigate. Thanks for the detailed report @zgosalvez

+15

paulb777 on Sep 19, 2018

For the various Unity SDK users on this thread, we just released the 5.3.1 SDK with the fix for this issue. https://firebase.google.com/support/release-notes/unity

stewartmiles on Oct 3, 2018

Fixed in Firebase 5.8.1

paulb777 on Sep 19, 2018

Hi everyone,

We’re working on patching the Firebase C++ and Unity releases to migrate them to the 5.9.0 iOS SDK. In the meantime, under Assets/Firebase/Editor/ there are a set of files matching *Dependencies.xml files (e.g AnalyticsDependencies.xml) that reference the iOS SDK version. You’ll need to modify the <iosPods> section of each file to reference iOS SDK 5.9.0 rather than 5.6.0. For example, in AnalyticsDependencies.xml change…

<iosPods>
    <iosPod name="Firebase/Analytics" version="5.6.0" minTargetSdk="8.0">
    </iosPod>
  </iosPods>

to…

<iosPods>
    <iosPod name="Firebase/Analytics" version="5.9.0" minTargetSdk="8.0">
    </iosPod>
  </iosPods>

stewartmiles on Sep 27, 2018

@phuong-unity @ozbra I solved it by adding <iosPod name="GoogleUtilities/MethodSwizzler" version="5.2.0"> inside Firebase/Editor/AppDependencies.xml next to the Firebase/Core entry.

hex on Sep 27, 2018

I’ll follow up with the Unity SDK team today on updating to at least the iOS Firebase SDK 5.8.1.

paulb777 on Sep 27, 2018

@ozbra You can see more about the link failure on the Xcode Report Navigator pane.

Also please do any follow up on one of the Firebase Unity support channels. See #1906.

Thank you for all those answers and guidance.

Thank you for redirection but the problem is Unity Firebase Unity support channels are not responding to anything. Similar question asked like 15 days but not a single proper answer yet. That is why I wanted to post here.

ozbra on Oct 19, 2018

Hi @RobertBateman, I had this exact issue yesterday.

The fix for me was to add the iosPod GoogleUtilities/MethodSwizzler xml line to AppDependancies.xml (per @hex’s suggestion) but do NOT change the version number(s) in *Dependancies.xml from 5.6.0 to 5.9.0 – just leave them as-is or you’ll get the FDLURLComponents file not found error, not sure what fix is for that.

MiketoString on Oct 2, 2018

Hi @MiketoString ,

yeah that fixed it.

Thank you kindly 😃

RobertBateman on Oct 2, 2018

A recent pod repo update or regeneration of the Podfile.lock file will expose the bug.

paulb777 on Sep 27, 2018

Analyzing dependencies [!] FirebaseAuth requires CocoaPods version >= 1.4.0, which is not satisified by your current version, 1.1.1.

@ozbra you just need to update your CocoaPods version. in terminal enter this command: gem install cocoapods

ghost on Sep 27, 2018

@jayahariv Thanks for the update. I’ll delete your comments here to keep this thread focused on original topic.

paulb777 on Sep 19, 2018

@paulb777, I can confirm that the workaround works. Thanks.

No problem; It’s the least I could do. Please keep us posted.

zgosalvez on Sep 19, 2018