Binary projects: Fall back to an xcframework when nothing else is available #3194
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The logic introduced in #3152 attempts to avoid downloading an xcframework when a user didn't ask for one. This is acceptable for GitHub Releases, where a source fallback is available, but not for xcframework-only binary projects. Projects which only advertise an XCFramework appear to succeed but download nothing when built without
--use-xcframeworks:(Notice that there's no
*** Downloading Foo binary at "x.y.z"event indicating that an actual binary was downloaded.)Fixed by causing binaryAssetFilter to behave differently for binary project URLs, and select unwanted xcframework releases as a last resort.