Thank you, Mark. The same problem persists in the official release. Fixed by your suggestion.
Hello guys, still couldnât figure it out can anyone help , and also I tried 2-3 different ways but didnât work. any updates?
Any news about how to fix this? Iâm having the same issue and after a good week of trying stuff I have not found a solution. I tried doing a fresh install of xcode because these errors only appear for me on xcode 16.2 when I run the project on 26 its fine. If I manage to find something I will let you know.
Iâm currently having the same issue on Xcode 26.0.1 but only on a UITest project. Everything worked perfectly on Xcode 16.4. Tried setting âExplicitly Built Modulesâ to no but still having the same issue.
But we are also using spm packages and pods together in one project. And the module thatâs missing is a pod.
How can this be fixed?
In case this helps someone else:
The variable name for Explicitly Built Modules changed in the project file between Xcode 16.4 and Xcode 26, and it doesnât appear to migrate automatically. We changed the variable on our desk computers running 16.4, checked it into github, then ran our jenkins test job and still ran into the same issue. The jenkins test job is running on a lab computer running Xcode 26. Finally running a diff on the file shows that we needed to update the variable name manually (or on an updated version) and check it back in before Xcode 26 would see the change.
Xcode 16.4 variable name: _EXPERIMENTAL_SWIFT_EXPLICIT_MODULES
Xcode 26 variable name: SWIFT_ENABLE_EXPLICIT_MODULES
Both show up with the same human readable name in Xcode build settings and if we update it in 16.4 then 26 didnât see it. We ended up manually editing the project.pbxproj file to add the new variable name and got past this issue.
1 Like
thinksďźI updated Xcode to 26.01, then I saw this error.
when I turn off Explicitly built, itâs all ok.