Post

Replies

Boosts

Views

Activity

Comment on Xcode 13 "Missing package product" using local Swift Packages
I'm getting this specific variation of this issue and I have found a solution. Just trick xcode into thinking that one local library is two: • Close all projects from menu bar or ctrl-option-cmd-w • Delete contents of ~/Library/Developer/Xcode/DerivedData • Delete any Package.resolved, .swiftpm or .build files in ALL packages that are local. • Create a symbolic link to the local library "ln -s MyLibrary MyLibraryII " ...
Mar ’23
Comment on Xcode 13 "Missing package product" using local Swift Packages
... • Don't touch Package/Project A, Package/Project B has to change package to the path of MyLIbraryII. You can now open one library in two seperate projects. Just keep in mind that it's jury-rigged.
Replies
Boosts
Views
Activity
Mar ’23
Comment on Xcode 13 "Missing package product" using local Swift Packages
I'm getting this specific variation of this issue and I have found a solution. Just trick xcode into thinking that one local library is two: • Close all projects from menu bar or ctrl-option-cmd-w • Delete contents of ~/Library/Developer/Xcode/DerivedData • Delete any Package.resolved, .swiftpm or .build files in ALL packages that are local. • Create a symbolic link to the local library "ln -s MyLibrary MyLibraryII " ...
Replies
Boosts
Views
Activity
Mar ’23