Could not find or use auto-linked framework 'Testing': framework 'Testing' not found

[pasllani]

Description

Xcode Version 16.4 (16F6)
iPhone 16 Pro Simulator (iOS 18.6)

I'm not able to build my project after adding this package to my project. I even created a brand new Xcode project with only the default code in it and added the package and saw the same issue.

This is the screenshot of the error from the blank Xcode project.

Reading online of people running into the same issue, some mentioned that setting ENABLE_TESTING_SEACH_PATHS to YES fixes the build issues, which it does, but then it fails to link to the simulator citing the same error above.

Checklist

• I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
• If possible, I've reproduced the issue using the main branch of this package.
• This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior

No response

Actual behavior

No response

Steps to reproduce

1. Create a brand new Xcode project.
2. Run the project and see that it builds and runs successfully.
3. Go to File -> Add Package Dependencies...
4. Paste in the link for swift-dependencies https://github.com/pointfreeco/swift-dependencies and tap Add Package.
5. Select the Project as the target for Dependencies, DependenciesMacros, and DependenciesTestSupport.
6. Build project and see errors.

Dependencies version information

1.10.0

Destination operating system

iOS 18.6

Xcode version information

Xcode Version 16.4 (16F6)

Swift Compiler version information

swift-driver version: 1.120.5 Apple Swift version 6.1.2 (swiftlang-6.1.2.1.2 clang-1700.0.13.5) Target: arm64-apple-macosx15.0

[mbrandonw]

• Select the Project as the target for Dependencies, DependenciesMacros, and DependenciesTestSupport.

Does this mean you are linking DependenciesTestSupport to your application target? If so, that is not correct. You should only link DependenciesTestSupport to your test targets in order to get access to a test trait that aids in testing with dependencies.

Since I don't believe this is an issue with the library I am going to convert it to a discussion. Please feel free to continue the conversation over there!

[pasllani]

That fixed it, thanks!