A framework builds for one architecture. iOS consumers need an XCFramework
A simulator-only framework works on your machine and fails on the device, and the error names a missing architecture rather than the packaging decision that caused it.
kmp
103 posts
commonTest runs on every target, which is the point and the cost
One test, five executions. That is how you find platform bugs — and how one flaky test fails five jobs.
composeResources is not Android resources, and qualifiers resolve differently
Same folder names, different resolution. The accessor is typed, and a missing qualifier fails somewhere new.
kotlinx-datetime has no Calendar, and the timezone database ships per platform
Instant is unambiguous. LocalDateTime is not. The same arithmetic can disagree across targets.
expect/actual is not an interface, and the difference shows up at link time
An interface is resolved at runtime by an instance. expect/actual is resolved at compile time by the source set.
The iOS framework you export is an API, and nobody reviews it
Every public declaration in the shared module becomes Swift API. internal is the design tool.
Your shared database needs a driver per platform, and that is the easy half
The driver is a one-line expect/actual. Threading, file location, and the OS deleting your file are the rest of it.
A DI module that compiles on every target and only works on one
Registration is common. The bindings are not. DI defers the error to first use, which is usually on a user's device.
Your Kotlin class becomes an Objective-C class, which is why the name is wrong
Obj-C has no namespaces. Everything exported is prefixed and flattened, and each Kotlin idiom loses something specific.
Kotlin/Native memory is not the JVM's, and a retain cycle crosses the bridge
Kotlin objects held by Swift are ARC-counted. A loop through both runtimes is invisible to both profilers.
One Gradle build, five outputs, and the cache that only helps three
Android and JVM targets cache well. Native link steps mostly do not, and that asymmetry is where your CI time goes.
One Ktor client, four engines, and the timeouts that don't mean the same thing
You configure one connect timeout. OkHttp, NSURLSession and the browser each enforce a different thing with it.