Testing failed: No such module 'ComposableArchitecture' #558
-
We've been experiencing a lot of issues with TCA on CI where the tests compile and pass but Xcode thinks that it can't find the module, and then fails it all. Possibly related to this issue: #22
The frustrating thing is that everything works locally, and this was only an occasional failure, but now it is happening 100% of the time (only on CI). Our CI is running Xcode 12.4 and we are running both Xcode 12.4 and Xcode 12.5 locally. I think that this is an Xcode / Swift Package Manager bug, and the best workaround might be providing alternative library packaging (like CocoaPods): #557 edit: workaround here #557 (comment) |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
Okay actually I can reproduce it locally, but only when testing via the command line (thru a fastlane lane). Will dig a bit deeper. |
Beta Was this translation helpful? Give feedback.
-
Are you using a custom build configuration name (ie, something other than FWIW we've never seen this issue in our CI, both with Xcode 12.4 and 12.5. |
Beta Was this translation helpful? Give feedback.
-
We are using some custom scheme names, e.g. # Podfile
project 'XXXX', 'Develop Debug' => :debug, 'Sprint Debug' => :debug, 'AppStore Debug' => :debug,
'Develop Release' => :release, 'Sprint Release' => :release, 'AppStore Release' => :release The target that is failing is an Xcode static library target
printed over and over, when compiling other unrelated source files in that same target. The top of the file looked like this: import ComposableArchitecture
import Swiftilities so I changed the order to this: import Swiftilities
import ComposableArchitecture and that may have fixed the problem. |
Beta Was this translation helpful? Give feedback.
-
Hi @chrisballinger, sorry you're having troubles, but this is most likely a bug in Xcode that needs to be worked around, so I'm going to move it to a discussion rather than an issue on this repo. |
Beta Was this translation helpful? Give feedback.
-
I can confirm that ditching SPM and using CocoaPods resolves this issue. Workaround here: #557 (comment) |
Beta Was this translation helpful? Give feedback.
I can confirm that ditching SPM and using CocoaPods resolves this issue. Workaround here: #557 (comment)