[Xcode 13.3] Fix for artifact not found for target #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
macblazer
requested changes
Mar 10, 2022
There was a problem hiding this comment.
Thanks for the PR for this, but there's a simpler fix that is a little better in the long run. If you want to remove the rename of the .xcframework file, then modify the two lines in the Package.swift we can accept this contribution.
Projects using the .xcframework directly (not through Swift Package Manager) are not impacted by a simple two line change to the Package.swift file.
|
As requested, I simply removed the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
With the upcoming version of Xcode 13.3 there seems to be a new behaviour for binary targets. It will throw an error (
artifact not found for target) if the xcframework file name is not identical with the binary target name.Proposed fix
Renamed the xcframework to
CertificateSDKPackage.xcframeworkand adjust thepathparameter of thePackage.swift.An alternative would be to rename the package completely and keep the name of the xcframework. This however might cause conflicts with projects that use the framework.
Reference
There is no real public documentation for this change, only one other thread here.
I was able to verify that fix solves the issue on Xcode 13.3 RC.