which carthage: /usr/local/bin/carthagecarthage version: 0.36.0xcodebuild -version: Xcode 12.3 Build version 12C33--no-build? No--no-use-binaries? No--use-submodules? No--cache-builds? No--new-resolver? NoCartfile
github "BranchMetrics/ios-branch-deep-linking"
binary "https://api.mapbox.com/downloads/v2/carthage/mobile-maps/mapbox-ios-sdk-dynamic.json"
Carthage Output
$ carthage bootstrap --use-netrc
*** Checking out ios-branch-deep-linking at "0.36.0"
*** Cloning ios-branch-deep-linking
*** Downloading binary-only framework mapbox-ios-sdk-dynamic at "https://api.mapbox.com/downloads/v2/carthage/mobile-maps/mapbox-ios-sdk-dynamic.json"
*** xcodebuild output can be found in /var/folders/d0/v6pnb6p12dd8l4xlmrtfrll9m3cttn/T/carthage-xcodebuild.hZwoO7.log
*** Downloading mapbox-ios-sdk-dynamic.framework binary at "6.3.0"
*** Downloading ios-branch-deep-linking.framework binary at "Branch iOS SDK 0.36.0"
Actual outcome
Binaries are downloaded but they're not copied to the local directory. They remain only in the Carthage cache directory .
~/Library/Caches/org.carthage.CarthageKit/binaries

Working Directory

Expected outcome
Carthage should copy the resolved binaries from the cache directory into the working directory.
Not sure if it's related to your issue @rcedwards, but I had a similar issue, related to the wrong framework typeIdentifiers on my machine: https://github.com/Carthage/Carthage/issues/3093 (see comments for what fixed my issue)
@chriscomeau wow crazy issue and yes this was also causing my problem! Thanks so much for linking me to your issue!!!
Duplicate of #3093
Most helpful comment
@chriscomeau wow crazy issue and yes this was also causing my problem! Thanks so much for linking me to your issue!!!
Duplicate of #3093