TCA does not work with Framework #1774
Answered
by
mbrandonw
kalupas226
asked this question in
Q&A
-
|
Hi, thank you for your great library. I use TCA a lot and have found that it works well for projects that consist of only the main app target or are multi-modularized by SPM. However, I have run into a problem this time. I am unable to build TCA on a project that is multi-modularized by Framework. The error log is as follows. expand error logsI have also looked at issues and discussions. And I found some similar ones. Also, removing a dependency on the "Dependencies" library will result in an error stating "undefined symbol: OrderedCollections". Is the only way to solve this problem to switch to multi-modularity with SPM? |
Beta Was this translation helpful? Give feedback.
Answered by
mbrandonw
Dec 28, 2022
Replies: 1 comment 3 replies
-
|
I don't believe this is an issue with TCA, but rather a long standing problem/bug with Xcode. It's the whole reason why we can't have a separate "test support" library for Luckily your situation is fixable. You just need to have your app target stop depending on TCA and Dependencies directly. You already get that transitively by depending on SimpleFramework:
|
Beta Was this translation helpful? Give feedback.
3 replies
-
|
Thank you for your quick response!
I could understand. Also it is sad.
Thank you for sharing your solution as well. However, I was able to solve this problem by having only one Framework with a dependency on TCA, and then transitively depending on that Framework for any dependencies on TCA, and not having a direct dependency on TCA. For example: classDiagram
MainAppTarget ..> FrameworkA: Dependency
MainAppTarget ..> FrameworkB: Dependency
FrameworkA ..> TCADependencyWorkaroundFramework: Dependency
FrameworkB ..> TCADependencyWorkaroundFramework: Dependency
TCADependencyWorkaroundFramework ..> ComposableArchitecture: Dependency
TCADependencyWorkaroundFramework ..> Dependencies: Dependency
It is a workaround, but I'm glad I could find a solution thanks to you. |
Beta Was this translation helpful? Give feedback.
-
|
@kalupas226 this the correct way to do it, we also do the same on our projects : having a shared framework which embeds TCA and allows to share TCA to multiple feature frameworks 👍 |
Beta Was this translation helpful? Give feedback.
-
|
@PierreCapo |
Beta Was this translation helpful? Give feedback.
Answer selected by
kalupas226
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I don't believe this is an issue with TCA, but rather a long standing problem/bug with Xcode. It's the whole reason why we can't have a separate "test support" library for
TestStore, which in turn is the reason we needed to build and maintain XCTestDynamicOverlay.Luckily your situation is fixable. You just need to have your app target stop depending on TCA and Dependencies directly. You already get that transitively by depending on SimpleFramework: