composeResources qualifiers are not Android's, and the fallback differs
A qualifier Android resolves may have no equivalent on iOS or the web.
All posts
A Compose UI test in commonTest runs five times and fails on one
The clock, the input source and the available fonts differ per target.
Compose for web loads a runtime before it draws anything
First paint waits on a wasm binary and a font, which no mobile profile shows.
Four crash reporters, one shared module, and the traces nobody could read
The reporting SDK is platform code and the crash is in shared code.
A deep link is four platform integrations wearing one URL
Verified, registered and delivered differently; parsing is the easy part.
Your default arguments do not exist in Swift
Swift sees the full parameter list, every time.
The same dp is a different number of pixels on every target
Density comes from the platform and the user's font scale multiplies it.
Dispatchers.IO is not in commonMain, and the reason matters
A browser has no thread pool to offload to.
There is no shared way to store a secret, and that is the correct answer
Keystore and Keychain hold a key your process cannot read.
An expect declaration cannot carry default arguments, and the error says otherwise
Defaults live on the expect side; the diagnostic points at the actual.
A Flow is cold, and that is why your ViewModel fires three network calls
Each collector re-runs the producer. Two UI observers plus a test is three executions.
A golden screenshot is a per-platform artifact, whatever the test says
Font rasterisation differs per renderer, so one reference image cannot hold.