Alamofire.xcframework -- is linked into -> Internal-Framework-A
Alamofire.xcframework -- is linked into -> Internal-Framework-B
Because Alamofire.xcframework is being linked into multiple internal frameworks, it will be linked without actual embedding. This means that AppTarget will need to link and embed Alamofire.xcframework so that the internal frameworks can dynamically link it at runtime.Internal-Framework-A -- is linked into -> AppTarget (actual application target)
Internal-Framework-B -- is linked into -> AppTarget
Internal frameworks compile correctly with this setup but AppTarget doesn't compile and it's trowing the follow error:
Multiple commands produce ... Command: ProcessXCFramework and the reason for that being:
on compile time AppTarget compiles Internal-Framework-A that triggers the ProcessXCFramework for Alamofire.xcframework but because AppTarget also has Alamofire.xcframework as dependency it will also run the ProcessXCFramework command, so we will have 2 commands for the same file.