TCA and transitive dependencies ("error: no such module 'CustomDump'") #2200
Unanswered
protonjohn
asked this question in
Q&A
Replies: 2 comments 1 reply
-
Temporary fix for this is not to use |
Beta Was this translation helpful? Give feedback.
1 reply
-
That's frustrating and a little confounding, since the error points at a file in a module that definitely depends on |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Our app has an Xcode project, but we're beginning to modularize it out into smaller local Swift packages within the project. Some of these modules contain our UI. These modules depend on the TCA library. The TCA library depends on a number of other things, one of them being the
swiftui-navigation
framework, which in turn depends onswift-custom-dump
. When trying to build the app, we end up getting the following compilation error from within the TCA project:This error goes away when we include TCA as a dependency directly from the application, but re-appears occasionally when we move modules around or change the dependency structure (I'm guessing SPM only does a low-depth recursion when resolving dependencies). We thought about adding all of TCA's dependencies themselves as the app's dependencies to resolve the issue, but before forcing things through without thinking, we wanted to see if anybody else has experienced something similar, and if this disappointing limitation of SPM is a recent regression or a long-standing issue known to Apple.
Beta Was this translation helpful? Give feedback.
All reactions