We're using Tuist v4.21.1 for all of our projects, but only one fails in a way you described. Currently I'm researching if Tuist is a root of problem by generating project with no Tuist optimizations / creating plain project by bare hands, I'll keep you updated

the .o files are present in ArchiveIntermediates of notification extension product after every try. if i can provide some more context to help resolving this issue — hit me up

encountering the same error with XCode 15.4, ios-only project re-generated every time by Tuist and all code in Swift Packages under version 5.10. the build goes well, tests is good too, but archiving for Debug configuration throws op error on ld for one of our feature packages to application's notification extension. archiving for Release configuration unexpectedly works like a charm 🤧 I can add that this error is not a complete blocker — if i'll retry enough it will pass on our CI after a few attempts. tried to archive failing package in Debug on my machine — works okay.