Hi @pepicrft,
thank you for your quick response and the warm welcome 
!
In your post you mentioned:
“Turns out that when you extract the resources of a target into an associated bundle, like we used to do, Xcode doesn’t synthesize the resource accessors because it doesn’t know the bundle resources are associated with the target.”
Since you are back to extracting resources of the targets into bundles, I imagined that this is the “expected” outcome. If that is not the case, I am happy to try and reproduce our issue in an example project.
As to our motivation for the Tuist adoption: As I mentioned, we have a very dependency heavy app and we’ve heavily been working on modularising it the past year. That really exposed the deficits of SPM as a project management tool. Uncontrollable Package resolving followed by invalided caches and long (CI) builds pushed us to look for a solution.