Xcode12.2 use Carthage install Firebase crashlytics and build error

[KC-218]

[REQUIRED] Step 1: Describe your environment

• Xcode version: 12.2
• Firebase SDK version: 8.4.0
• Installation method: Carthage
• Firebase Component:

And I want to use Crashlytics in Xcode12, What's wrong with my issue?

[REQUIRED] Step 2: Describe the problem

Steps to reproduce:

What happened? How can we make the problem occur? Build the APP and got an error

ld: in /Users/xx/Desktop/xx/xx/xx/xx/xx/xx/xx/xx/Carthage/Build/iOS/FirebaseRemoteConfig.framework/FirebaseRemoteConfig(FIRConfigValue.o), building for iOS Simulator, but linking in object file built for Mac Catalyst, file '/Users/xx/xx/xx/xx/xx/xx/xx/xx/xx/xx/Carthage/Build/iOS/FirebaseRemoteConfig.framework/FirebaseRemoteConfig' for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation)

And I use these commands to install frameworks.

carthage update --platform iOS --no-use-binaries --use-xcframeworks
or
carthage update --platform iOS --no-use-binaries

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

[gronico]

And the error is?

[paulb777]

--no-use-binaries might be an issue since Firebase only supports binaries.

Duplicate question at https://stackoverflow.com/questions/68630216/xcode12-2-use-carthage-install-firebase-crashlytics-and-build-error

[google-oss-bot]

Hey @Bruce9487. 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.

@Bruce9487 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.