We started seeing this after enabling K/N build cache (removing

kotlin.native.cacheKind=none

basically)

Does it need to be applied in all modules perhaps?

The task that is failing with that message will tell you a lot. You should only need that plugin in the module making a framework, and only if it's a dynamic framework. However, tests are the complex part. Disabling the compiler cache used to allow tests to work. Before that, as long as you didn't reference anything from bugsnag in your test code (including setup, any referenced code, etc), the Kotlin compiler would simply strip out the code that held references to bugsnag, and you'd be fine. At some point in the last few versions, tests started to be built with dynamic binaries, so they include all of your code. This presumably sped up the compilation for tests, but forced symbol resolution. Our recent issue is, as much as I'd rather not disable the cache, that also appears to not work anymore.

Solutions are still being discussed (but our backlog is currently pretty long, so I'm not sure when we'll sort that out). • Add bugsnag with CocoaPods in Kotlin. Not a good way to go, for a number of reasons, but that will make the symbols available. • Create a "stub" binary to satisfy the linker for the test compilation. Assuming you never call it (and in a test, you probably shouldn't), that would work. We were doing something like that 1+ years ago. • Figure out if we can just call the Objc dynamically for Bugsnag and Crashlytics, then you don't really have to worry about any of this, and it solves another current issue we have that most don't.

If you're using an "umbrella" module to create the framework, and you don't need to test any code there, just make sure there are no tests for K/N to run, and it should skip that step.

But, step one, which task is failing? That'll dictate the options.

If you're not running tests in that module, but you are exporting a framework (it doesn't need to be an umbrella module), the linker plugin should work, but if you're using that and its not working, I assume the test build is failing.

But yeah, it’s the

linkDebugTestIosSimulatorArm64

task that fails

Perhaps we did not define the

iosTest

task correctly? We have this “umbrella” task defined:

project.tasks.register("iosTest") {
  description = "Executes Kotlin/Native unit tests for all available targets."
  group = "Verification"

  // For running tests on an arm64 compatible host.
  project.tasks.findByName("iosX64Test")?.let {
    dependsOn(it)
  }

  // For running tests on host that are arm64 compatible.
  // For running tests on a non-arm64 compatible host.
  project.tasks.findByName("iosSimulatorArm64Test")?.let {
    dependsOn(it)
  }
}

This was set up before we enabled hierarchical project structure. It doesn’t look like

iosTest

Gradle is provided out of the box either way.

Thinking through how to go about disabling K/N tests on a specific module

Disabling K/N tests for the module fixes that particular problem but now Compose Multiplatform linking breaks 😃

This is our baseline set up right now. I ended up doing following: • enabled K/N build cache • set

isStatic = true

on the XC Framework module • remove applying crashkios plugin • Disable K/N tests for the

:shared:bugsnag

module Everything compiles fine but getting Compose Multiplatform linking warnings now and a runtime crash on iOS:

w: <bitkey.shared.state-machine.ui:public> @ /Users/zhukov/Development/wallet/app/shared/state-machine/ui/public/src/iosMain/kotlin/build/wallet/statemachine/recovery/cloud/CloudSignInUiStateMachineImpl.kt:37:5: Function 'LaunchedEffect' can not be called: No function found for symbol 'androidx.compose.runtime/LaunchedEffect|-576771147392862334[0]'
w: <missing declarations>: No function found for symbol 'app.cash.molecule/launchMolecule|-7305106088441339121[0]'
w: <missing declarations>: No function found for symbol 'androidx.compose.runtime/remember|1835138394250687683[0]'
w: <missing declarations>: No function found for symbol 'androidx.compose.runtime/remember|-2596345568877061727[0]'

Unrelated to Crashkios at this point.

Looks like this is the latest state of things https://github.com/JetBrains/compose-multiplatform/issues/3611#issuecomment-1705644654 🤷

Thanks!

Second message says something about the compiler