You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Technically, one repo can only define one package.swift. You can define a package in a sub folder, but there is no way for another project to include it. If you define a package in a sub folder and reclaim the same module in the root package, it works, but when you open the project from the root package, xcdoe won't show the source code in the sub folder.
In a nutshell: since Xcode 11.4, it seems that your project will only use .static libraries, and if your library is present twice or more in your project (2 different targets that use the same library, for example an iOS app target and its Today Widget). You can lead to a duplication of static library. I suspect it was the case before Xcode 11.4, but no complains whatsoever... Since I applied the trick in this tutorial, my app shrunk a little in size, maybe due to the fact that my App and its Widget use the exact same code and not a duplicated one.
An easy fix is to force the library to be .dynamic, but it requires either to ask the library maintainer to update his Package.swift definition, or fork the library yourself to do so. For me, it's not a solution 🤔.
Constraint:
The text was updated successfully, but these errors were encountered: