Add support for XCFrameworks with .dylib libraries #6133
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.
Tuist should not error when an XCFramework contains .dylib libraries
Short description π
According to the XCFramework documentation "an XCFramework can include dynamic library files" for macOS. This indeed works without fail and should be allowed. However, the documentation is wrong or outdated for iOS and iOS Simulator. These platforms also allow .dylib libs in an XCFramework.
Tuist does not allow dynamic library files even for macOS. Using an XCFramework containing .dylib files, regardless of platform, throws a "XCFrameworkMetadataProviderError.supportedArchitectureReferencesNotFound" error and prints "couldn't find any supported architecture [...]" which, at the very least, is misleading.
How to test the changes locally π§
Contributor checklist β
mise run lint:fix
Reviewer checklist β
changelog:added
,changelog:fixed
, orchangelog:changed
, and the title is usable as a changelog entry