I'm in the process of upgrading a Kotlin Multiplatform project to Kotlin 1.3.20. I quickly ran into the following error while linking the

iosX64

target:

ld: '/Users/.../.konan/dependencies/libffi-3.2.1-2-darwin-ios_sim/lib/libffi.a(ffi64_x86_64.o)' does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target. for architecture x86_64

Which seems to be a result of bitcode being enabled by default in Kotlin 1.3.20. So I've tried disabling it for all my iOS targets by adding the following to each target:

binaries {
   framework {
       embedBitcode('disable')
   }
}

Unfortunately this doesn't resolve the error. I'd appreciate any suggestions on what to try next?

This should work. Can you show the entire Gradle script?

My experiments with your build scripts show that

embedBitcode

should fix the issue. Have you tried to do a clean rebuild?

Interesting, I did a clean rebuild, I even tried removing the

.gradle

dir and the build folders manually. But no change.

What task does report the report?

It happens while linking the iosX64 build (the simulator):

./gradlew clean linkMainDebugFrameworkIosX64

The root cause is that this build script creates two frameworks: one using the old

compilation.outputKinds

DSL method and another using the binaries DSL (

binaries { framework { ... } }

). And disabling bitcode embedding affects only the framework created by the binaries DSL. So you can just drop using

compilation.outputKinds

and use only the binaries DSL.

That makes a lot of sense! I've made the changes to my build file and the build is progressing again. Just a few more minutes for the build to complete...

FYI Xcode has two build caches and only one of them is erased during a clean operation. The other is called Derived Data. There’s a shortcut to navigate to it via the settings screen’s locations tab. On rare occasion when really weird errors are happening it’s because derived data has a bad cache of a framework. Deleting the contents of that directory will fix it.

@Sam Thanks Sam, I found that cache earlier on as well. After deleting it though it didn't get filled again. So that cache wasn't touched during the Kotlin build process.

Interesting. It must be only for things that Xcode itself builds. If your project starts to pull in 3rd party libraries written in ObjC or Swift then you’ll need that directory one day. 👍