A Kotlin crash on iOS arrives without a usable stack trace
The dSYM for the shared framework is produced by Gradle and uploaded by nobody.
kmp
103 posts
The text field that dropped characters on one target only
IME composition, autocorrect and hardware keyboards reach Compose differently per platform, so state hoisted too far loses keystrokes on exactly one of them.
Back means four different things, and shared navigation has to pick
A hardware button, an edge swipe, a window close and a browser history entry are not the same event. One shared handler gets at least two of them wrong.
The coroutine that kept collecting after the screen was gone
Android cancels viewModelScope for you and SwiftUI does not. One scope, two lifetimes, and only one of them has a callback that fires when the screen ends.
Your dependency graph has six entry points and one of them runs twice
Application.onCreate, a Swift app init, a main function and a page load each start the graph. Two inits on one platform is a duplicate-definition crash at the worst moment.
Your HTTP cache exists on two targets and is a stub on two others
OkHttp and NSURLSession cache to disk, the browser's cache is the browser's, and the common engine has none. Measured hit rates differ by a factor nobody budgeted for.
appleMain exists only if your targets justify it
The hierarchy template inserts nodes based on declared targets. A directory for a node that does not exist compiles nowhere and warns about nothing.
Dispatchers.Main throws on a target you forgot to configure
Main is supplied by a platform integration, so it exists on Android and iOS and fails at runtime on desktop tests — a crash whose message names a module, not a mistake.
We shared 60% of the code and one platform used all of it
Measured per target rather than per line: the iOS app reached a third of the shared surface because the API was shaped around Android's lifecycle.
The transaction that was atomic on Android and not on the web
Nested transactions, savepoints and write locking vary per driver. Code written against one driver's guarantees loses them silently on another.
One version, four numbering schemes, and a release that could not be rolled back
A monotonic integer, a build string, a semantic version and a cache-busting hash have to agree. Deriving all four from one source is the only shape that survives a hotfix.
Nothing reconnects your WebSocket, on any target
A dropped socket is a normal event with no exception on some engines. Reconnection with jitter and a resume token is application code, and it is the same code on all four.