Carthage update pulls in incompatible versions of FirebaseAnalyticsBinary and FirebaseCrashlyticsBinary

[JuliusBahr]

[REQUIRED] Step 1: Describe your environment

• Xcode version: 11.5
• Firebase SDK version: 6.9
• Firebase Component: Analytics, Crashlytics
• Component version: _____
• Installation method: Carthage version 0.35.0

[REQUIRED] Step 2: Describe the problem

Steps to reproduce:

In your Cartfile add: binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAnalyticsBinary.json" binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseCrashlyticsBinary.json"

Call carthage update --platform iOS

What happened? How can we make the problem occur? The downloaded FirebaseAnalyticsBinary and FirebaseCrashlyticsBinary are incompatible with one another and lead to linker errors.

Workaround

Set an explicit version of the dependency. I used: binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAnalyticsBinary.json" ~> 6.9 binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseCrashlyticsBinary.json" ~> 6.27

[ryanwilson]

Hi @JuliusBahr - sorry for the issues you're seeing. Can you please share what the linker errors are so we can better understand the issue at hand? Thanks!

[JuliusBahr]

@ryanwilson I'm sorry I don't have logs anymore. The linker issue was around PromisesObjC.framework. But not the signing issue seen with iOS 13.3.x. I updated from a pretty old version of Fabric/Crashlytics to the FirebaseCrashlytics. When I updated FirebaseAnalytics and FirebaseCrashlytics PromisesObjC was not updated. That is where I ran into linker issues. This was only resolved when I explicitly set the versions in Carthage to the latest versions for both FirebaseAnalytics and FirebaseCrashlytics. Without setting versions I got into a state were FirebaseCrashlytics and FirebaseAnalytics did not create a new version of PromisesObjC.

[JuliusBahr]

The issue should be readily reproducible.

[paulb777]

This isn't obviously reproducible. I suspect something about the environment was stale or corrupt. We'll likely need a repro to make progress.

[google-oss-bot]

Hey @JuliusBahr. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@JuliusBahr if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.