Most mocking libraries do not work in commonTest, and the fix is better anyway
Dynamic proxies need a JVM. What replaces them asserts on outcomes instead of calls.
Engineering
Compose, Kotlin, and multiplatform work — the mechanism under the symptom.
296 posts
The test that only failed on wasm was measuring the environment
A single-threaded target surfaces every real-clock dependency a JVM run hides.
A klib is not a jar, and that changes how dependencies resolve
Metadata, klibs and platform artifacts resolve through different Gradle variants.
The module boundary that only the build file enforced
A layering rule nobody can violate is a dependency declaration, not a document.
A sealed hierarchy exports as an open class, so Swift cannot switch on it
Exhaustiveness is why you used a sealed type, and it is exactly what does not cross.
A staged rollout you control on one store and not on the others
Four channels, four halt latencies, and only one of them is under your hand.
actual typealias looks like a shortcut and changes what you promised
Aliasing to a platform type exports that type's whole surface to every caller.
The shared module cost 400KB on Android and 11MB on iOS
Android shrinks against a runtime already on the device. iOS links yours in.
Kotlin/Native's memory model changed, and your atomics did not
Freezing is gone, so the bugs it prevented at compile time are runtime bugs now.
There is no shared background work, because three platforms disagree about when
WorkManager schedules under constraints, iOS grants windows, the browser has none.
The biometric prompt belongs to the OS, and it can disappear mid-call
You suspend across a UI the system presents and may destroy without telling you.
Why the build cache helps the JVM target and almost never the native ones
Cache keys for native compilation include the toolchain, so they rarely hit.