kotlin-native | Kotlin/Native infrastructure | Compiler library

The latter error suggests you to synchronize the Kotlin version you're using and the Ktor version. Check the Recommended kotlinx library versions for details. Probably, you will need to change the Kotlin to 1.5.30, or downgrade the Ktor 1.5.4.

Please comment below with the result. I'll update this answer if something will be still wrong.

The gradle sync fails because CIO engine only supports java, and any dependency included in common part should be multiplatform(native).

Just move implementation("io.ktor:ktor-client-cio:$ktorVersion") into jvmMain dependencies.

There's no engine that can be added to common code, so you need to add an appropriate engine for each platform you support, and HttpClient() will pick one of them by itself. Check out documentation for more details

As a workaround, you can manually install libtinfo.so.5 to your system

e.g Linux distro package manager

Kotlin/Native does not offer interop with pure Swift. Currently it works indirectly with a K\N - Obj-C - Swift interop. Direct interoperability with Swift is on the roadmap, but it's currently paused AFAIK

From the documentation:

Kotlin/Native provides bidirectional interoperability with Objective-C" ... "A Swift library can be used in Kotlin code if its API is exported to Objective-C with @objc. Pure Swift modules are not yet supported.

Since SwiftUI is pure Swift, you can't really import it to Kotlin unfortunately (hopefully yet).

I confirm what you say about NSString.stringWithFormat. The feature is missing as we read in the JB offical answer from Svyatoslav Scherbina and we could follow the issue from you here: KT-42925

As an awful workaround, I was suggesting something like that (WARNING: not exhaustive, without many index count checks...)

building for iOS-armv7 but attempting to link with file built for iOS-arm64

Looks like you're trying to archive for armv7, which (I think) is 32 bit ios, or maybe watch, etc. Most apps need just arm64, and your Xcode framework will only be arm64 according to this:

This particular problem seems to be caused by the dash in the pod's name. There was already an issue reported on GitHub. For now, it's recommended to workaround this problem by re-naming the module. Changing your kotlin-library/build.gradle.kts like

The approach you've taken is pretty much correct and the way it's supposed to be done.

The thing I would add is, instead of passing around a pointer around. You should pass around a frozen FileLogger, which will internally hold a reference to a AtomicRef, the the attaching and detaching should be done internally. Especially since DetachedObjectGraphs are invalid once attached.

Maybe it will make sense to check the contents of your result .klib to make sure you use the correct package name. It can be done using ~/.konan/kotlin-native-macos-1.3.61/bin/klib CLI tool.
Also, I would recommend you to take a look at this sample from the Kotlin/Native Github, it also utilizes AFNetworking and uses the latest compiler version.