Hello. Our project has multiple targets. The Add Package UI allows adding to a single target but it's straightforward to add packages to other targets later, except this package. I'm not sure what's different.
Here's our project and packages:
When I initially add the package it gets added to the app target. For the other targets we just add the packages through the Frameworks, Libraries, and Embedded Content in the General tab for the target:
When you click the Add button all the other packages show up but not WebRTC:
One possible clue: I looked through all thePackage.swift files and the only significant difference is yours is the only one with .binaryTarget in the targets array.
Note that it seems possible to add the package through the Add Other... button but when you choose Add Package Dependency... there it's the original Add Package UI and I'm reluctant to go that way because I think we'll end up with another copy of WebRTC which is not what we want.
isadon
commented
1 year ago
Hello. Our project has multiple targets. The Add Package UI allows adding to a single target but it's straightforward to add packages to other targets later, except this package. I'm not sure what's different.
Here's our project and packages:
When I initially add the package it gets added to the
apptarget. For the other targets we just add the packages through the Frameworks, Libraries, and Embedded Content in the General tab for the target:When you click the Add button all the other packages show up but not WebRTC:
One possible clue: I looked through all thePackage.swift files and the only significant difference is yours is the only one with
.binaryTargetin thetargetsarray.Note that it seems possible to add the package through the Add Other... button but when you choose Add Package Dependency... there it's the original Add Package UI and I'm reluctant to go that way because I think we'll end up with another copy of WebRTC which is not what we want.