My cocoapods config looks like this:

cocoapods {
        name = "SharedModule"
        summary = "Shared business logic for our ios and android apps"
        homepage = "<https://github.com/myorg/myrepo>"
        ios.deploymentTarget = "14"
        extraSpecAttributes["libraries"] = "'c++', 'sqlite3'"
        license = "BSD"
        extraSpecAttributes.put("swift_version", "\"5.0\"") // <- SKIE Needs this!
        framework {
            baseName = "SharedModule"
            linkerOpts.add("-lsqlite3")
            export(project(":core:models"))
            export(project(":feature:program"))
            isStatic = true
        }
        xcodeConfigurationToNativeBuildType["TS-DEBUG"] = NativeBuildType.DEBUG
        xcodeConfigurationToNativeBuildType["DK-DEBUG"] = NativeBuildType.DEBUG
        xcodeConfigurationToNativeBuildType["KS-DEBUG"] = NativeBuildType.DEBUG
        xcodeConfigurationToNativeBuildType["OA-DEBUG"] = NativeBuildType.DEBUG
        xcodeConfigurationToNativeBuildType["BA-DEBUG"] = NativeBuildType.DEBUG
        xcodeConfigurationToNativeBuildType["TS-PROD"] = NativeBuildType.RELEASE
        xcodeConfigurationToNativeBuildType["DK-PROD"] = NativeBuildType.RELEASE
        xcodeConfigurationToNativeBuildType["KS-PROD"] = NativeBuildType.RELEASE
        xcodeConfigurationToNativeBuildType["OA-PROD"] = NativeBuildType.RELEASE
        xcodeConfigurationToNativeBuildType["BA-PROD"] = NativeBuildType.RELEASE
    }

Could you share more of the build log that has the

Failed to build module 'SharedModule';

in it?

yep. nothing.

@Tadeas Kriz deleting my DerivedData seems to have solved it. I have another dev on the team who was running into the same issue, but his actual build failed. After talking with him, his build started working as well, and I think maybe I know what was happening. Perhaps you can tell me if this sounds right. So, he did

pod install

and then opened our ios app workspace in Xcode. It showed the same error I was seeing. He did a build, and the build DID fail. But it also included several new errors about Ambiguous (kotlin) types. Those are known errors that we had. In version 0.0.15 of our KMM library we had configured the framework with transitive exports (oops):

export(project(":core:models")) { transitiveExport = true }
export(project(":feature:program")) { transitiveExport = true }

I then published a new version (0.0.16) that removed the transitive exports, and update the app to use version 0.0.16 When my other dev pulled the updated app project, and then opened it in Xcode, he still saw the “Failed to build module …” error in the IDE. But then, when he did a build (CMD+B), it succeeded. The “Ambiguous type” errors are gone, but the other error still shows up. I had him do Product > Clear all Issues to remove it, and then do another build, which also succeeded. Now, he can close and open the project in xcode and it all works fine. So, I think that originally there WAS a build error due to the exporting of transitive dependencies in the kmm library, but until trying to do a build, the Xcode IDE would just show “Failed to build module ‘SharedModule’. SDK is not support by the compiler…“. Only after doing a build would you see the REAL errors. And then once that issue was fixed (in the new 0.0.16 version), the build would work fine, but Xcode was still showing that original error because of, as you put it, “a weird Xcode caching issue”. And once we “manually” told xcode to clear it’s issues list, it went away and does not come back, because there is no issue. Does that seem right?