Selective testing for non-generated projects

Announcements
14

Good morning, @marekfort it turns out that this bug only happens when having two targets with Alamofire dependencies and each target having a different platform.

Maybe there’s a more minimal reproduction.

The attached sample is an iOS and tvOS app (and some test targets that Xcode added automatically, but I think they shouldn’t matter).

The podfile is this:

# Uncomment the next line to define a global platform for your project
# platform :ios, '9.0'

target 'AlamoSampleTwo' do
  # Comment the next line if you don't want to use dynamic frameworks
  use_frameworks!
  platform :tvos, '18.0'

  # Pods for AlamoSampleTwo
  pod 'Alamofire', '~> 5.3'

  target 'AlamoSampleTwoTests' do
    inherit! :search_paths
    # Pods for testing
  end

  target 'AlamoSampleTwoUITests' do
    # Pods for testing
  end

end

target 'AlamoSampleTwoMobile' do
  # Comment the next line if you don't want to use dynamic frameworks
  use_frameworks!
  platform :ios, '18.0'

  # Pods for AlamoSampleTwo
  pod 'Alamofire', '~> 5.3'

  target 'AlamoSampleTwoMobileTests' do
    inherit! :search_paths
    # Pods for testing
  end

  target 'AlamoSampleTwoMobileUITests' do
    # Pods for testing
  end

end

AlamoSampleTwo.zip (497.1 KB)

tuist graph will fail with either Alamofire-iOS-Alamofire or Alamofire-tvOS-Alamofire missing depending on timing.

I think Cocoapods changes some stuff when you depend on something on different platforms.