Cache issues when a target supports macOS and Mac Catalyst

[pepicrft]

What problem or need do you have?

As reported here by @NachoSoto, when there's a target in the graph that supports macOS and Mac Catalyst as destinations, the creation of the XCFramework fails because both frameworks have the same triple:

/usr/bin/xcrun xcodebuild -create-xcframework 
-archive /private/var/folders/60/737rrmcs6yqbfbl9fd4g0dcw0000gp/T/TemporaryDirectory.5gwC7A/Archives/iOS/simulator.xcarchive 
-framework _CollectionsUtilities.framework 
-archive /private/var/folders/60/737rrmcs6yqbfbl9fd4g0dcw0000gp/T/TemporaryDirectory.5gwC7A/Archives/iOS/mac-catalyst.xcarchive 
-archive /private/var/folders/60/737rrmcs6yqbfbl9fd4g0dcw0000gp/T/TemporaryDirectory.5gwC7A/Archives/iOS/device.xcarchive 
-framework _CollectionsUtilities.framework 
-archive /private/var/folders/60/737rrmcs6yqbfbl9fd4g0dcw0000gp/T/TemporaryDirectory.5gwC7A/Archives/macOS/device.xcarchive 
-framework _CollectionsUtilities.framework -output /var/folders/60/737rrmcs6yqbfbl9fd4g0dcw0000gp/T/TemporaryDirectory.5gwC7A/xcframeworks/_CollectionsUtilities.xcframework 
-allow-internal-distribution

-framework _CollectionsUtilities.framework 

Fails with:

A library with the identifier 'macos-arm64_x86_64' already exists.

[pepicrft]

@NachoSoto I started looking into this one. We have some logic in place that narrows down the destinations of external dependencies based on the destinations of your project targets. My hunch is that there might be some bug in that logic that leads to the wrong destinations, but I want to check with you first. Does your project have any target that has Mac Catalyst as a valid destination?