When integrating dependencies it seems that Tuist isn't integrating them directly (at least not with SPM dependencies). Instead it creates wrapper project to be able to manipulate linking type. Additionally it extracts all resources into separate bundle probably to avoid collisions when linking is static. Since resources are defined in separate bundle Xcode isn't generating resource symbols (that could be accessed from "code" target) which causes compilation fail.
Description
When integrating dependencies it seems that Tuist isn't integrating them directly (at least not with SPM dependencies). Instead it creates wrapper project to be able to manipulate linking type. Additionally it extracts all resources into separate bundle probably to avoid collisions when linking is static. Since resources are defined in separate bundle Xcode isn't generating resource symbols (that could be accessed from "code" target) which causes compilation fail.
cc: #317
Jira Issue
-