Fix compilation search paths error for 'Testing' in consumer app targets#118
Merged
Conversation
440edac to
edde389
Compare
This file contains hidden or 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
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.
Description
This PR resolves a compilation failure encountered when importing
SwiftUI-UDFin non-test consumer targets (like standard iOS applications).Problem
In recent versions, the
import Testingstatement was added toUDF/Store/TestStore/TestStore.swift. BecauseTestStore.swiftis packaged inside the mainUDFtarget (a regular library product) instead of a test target or test-support module, Xcode builds this file whenever the library is compiled.When a consumer app target compiles, the compiler encounters the
import Testingline but fails because standard app targets do not include Apple's Swift Testing framework (Testing.framework) in their developer search paths. This results in the following compilation error:Solution
The
import Testingstatement inTestStore.swiftis entirely unused by the class implementation. This PR removes the unused import, allowing the module to compile successfully for all consumer configurations without requiring special framework search paths in non-test targets.Verification
xcodebuildfor the consumer's app target.'Testing'dependency resolution error is gone and the target compiles successfully.