This PR fixes the matching of prebuilt items and their corresponding spec during the post-install phase.
Let's consider the following scenario:
A Foo pod produces the Foo.xcframework built item.
An unrelated Bar pod contains the Foo subspec, and produces the Bar.xcframework built item.
Pod::Specification::module_name returns Foo for both the Bar/Foo and Foo specs.
When looking up the spec for the Foo.xcframework built item, the previous logic would match Bar/Foo first. This leads to the following:
Foo.xcframework is copied inside the Prebuilt/Bar folder instead of Prebuilt/Foo.
The Prebuilt/Foo folder is left unchanged.
The proposed changes aim to prevent this by making sure that we check name equality between the built item and the spec's module_name for root specs first. If no matches are found in root specs, the existing fallback would apply.
This PR fixes the matching of prebuilt items and their corresponding spec during the post-install phase.
Let's consider the following scenario:
Foopod produces theFoo.xcframeworkbuilt item.Barpod contains theFoosubspec, and produces theBar.xcframeworkbuilt item.Pod::Specification::module_namereturnsFoofor both theBar/FooandFoospecs.When looking up the spec for the
Foo.xcframeworkbuilt item, the previous logic would matchBar/Foofirst. This leads to the following:Foo.xcframeworkis copied inside thePrebuilt/Barfolder instead ofPrebuilt/Foo.Prebuilt/Foofolder is left unchanged.The proposed changes aim to prevent this by making sure that we check name equality between the built item and the spec's
module_namefor root specs first. If no matches are found in root specs, the existing fallback would apply.