Skip to content

Fail early if expected XCFramework is not present #2725

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

neonichu
Copy link
Contributor

@neonichu neonichu commented May 4, 2020

Cherry-pick #2722 to the 5.3 branch.

Currently, we rely on a build failure if an expected XCFramework isn't
present in a downloaded ZIP. We should instead check if the expected
XCFramework is present while extracting the ZIP so that we can surface
this error already during package loading.

rdar://problem/60619547

(cherry picked from commit 0647265)
@neonichu
Copy link
Contributor Author

neonichu commented May 4, 2020

@swift-ci please test

Copy link
Contributor

@rballard rballard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved pending CI completion.

@neonichu neonichu merged commit 85c9cf4 into swiftlang:release/5.3 May 4, 2020
@neonichu neonichu deleted the fail-on-xcframework-name-mismatch branch May 4, 2020 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants