Not being able to depend on ComposableArchitecture from multiple dynamic frameworks is due to TCA being statically linked, or it is specifically something that you can't do when macros are involved?

It is due to depending on a static library from dynamic libraries, and is just a general limitation of the build system.

In case anyone bumps into this discussion, I have one more (unfortunate) update: although linking TCA to only one "common" framework enables the project to compile, I faced two more issues:

• I cannot build the project via CLI (e.g, xcodebuild build -project <project> -scheme <scheme> -sdk iphonesimulator | xcbeautify) because of the same macro error. Only building from Xcode works.
• Xcode is acting out almost all TCA related code are marked with errors and code completion doesn't work. Again, while Build and Run works.

Eventually, I'm following Brandon's advice and drop Xcode framework targets and instead migrate to SPM package libraries. I was able to combine Xcodegen and SPM local packages in a way that feels reasonable. Modules are defined in a Package.swift file and the application, extensions, schemes and a few other things are still configured with Xcodegen.

I faced the exact issue in XCode 16.1 Beta. We have a common package that has the TCA dependency. Before running the main target, build the common package with the TCA once. After building the Common package, run the app; these errors should disappear.

I might be wrong here, as it was a while ago when I was wrangling with this, but I remember that custom Build Configurations could also interfere with macros. In SPM, "Debug" and "Release" are baked in, and the only available configurations. If your application target scheme uses custom build configurations (e.g, "Mock", "Staging", etc.) Xcode breaks and it displays the errors above. Previews don't work either.

What's frustrating, is that you can still compile, build, and run the project on both the simulator or a physical device. However, not having code completion and tripping over hundreds of inline errors is a dealbreaker.

To sum up, keeping the project setup "as vanilla as possible", defining modules as SPM packages, relying on the default "Debug" and "Release" configurations, etc. is the way to go, I can confirm that both Composable Architecture and other macro based dependencies work like a charm.

@gyulavoros Hey I just renamed my configuration as Debug / Release and all the macro errors disappeared.
I was struggling for weeks because of this issue, code completion was completely broken.
But you just saved my life thank you. 👍