Throwing across the bridge loses your exception type
Swift sees NSError with a wrapped message, so a typed catch becomes a string match.
ios
18 posts
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.
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.
A Flow does not cross to Swift. A callback does.
Exporting a Flow hands Swift something it has no way to collect.
CocoaPods or Swift Package Manager: the choice belongs to the iOS team
Each channel constrains your publishing pipeline differently.
Every list you hand to Swift is copied, and the cost is per call
A Kotlin List becomes an NSArray by conversion, not by reference.
Your default arguments do not exist in Swift
Swift sees the full parameter list, every time.
Two Kotlin classes, one Objective-C name, and a header that will not compile
Objective-C has no namespaces, so two same-named classes export as one.
@MainActor and Dispatchers.Main are two different promises
Both mean the main thread and neither knows about the other.
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.
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.
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.