OK. For context, I wrote this version of Koin and we’re working to get this into Koin 3. The design is that all interaction with Koin happens in the main thread, we can keep Koin’s internals from freezing. The idea is that for the most part you access DI from the main thread. Making Koin accessible to any thread means everything internal is frozen, or we need to block and jump threads to access it.

The “block and jump threads to access it” is what I want to add. It would be a special version of inject (and associated calls). However, doing that means whatever you’re accessing will be frozen to allow that to happen. Ultimately, I want your code to decide if your state is being frozen. Koin isn’t going to surprise freeze anything.

Keeping a singleton unfrozen, and accessing it from multiple threads, will be quite difficult. There are basically 2 options. You can have the equivalent of “thread local” rather than “singleton”, and you can only ever get it from one thread. There could be some kind of “instance count” that is global and limited to 1, thereby being an effective singleton, but I’d really like to get my head around what the use case is here.

The other option is to have an unfrozen object instance in “limbo”, from a memory perspective. Then have it attach to whatever thread you’re accessing it from, then when you’re done, detach. Other callers would block waiting for it. This is one of those things that sounds nice but will be a nightmare in practice. We don’t do any unfrozen state transfer in our code. You rarely need to do it, and there are a number of potential issues: https://dev.to/touchlab/kotlin-native-transferring-state-4n8i

Hi everyone! happy to be here and thank you for creating this community!

I was looking at the KaMPKit and I'd like to understand better: • what are the benefit of using Koin instead of injecting objs from the constructor? (in the shared module) • what is cocoapodsext and where I can find its documentation? • what is the meaning of "-Xg0"?

“what are the benefit of using Koin instead of injecting objs from the constructor? (in the shared module)” - It’s kind of up to you. We’re doing a bunch of the Koin multiplatform work, so we included it in the sample. The sample itself is pretty minimal and you certainly don’t need Koin if you don’t want it.

“what is cocoapodsext and where I can find its documentation?” We forked the cocoapods plugin from Jetbrains so we could have some more flexibility. Dev is ongoing. The original goal was to enable a dynamic framework so we could get debugging to work again, but there are other configuration options we’d like to add. https://github.com/touchlab/KotlinCocoapods

Specifically we added

isStatic = false

to the config section

Thanks @kpgalligan!! 💯

How would I add the shared code as an external library to the apps?

Replace

implementation(project(":shared"))

with

implementation("com.example:shared:+")

or so. How would that work?

@Friedger The other multiplatform libs (ktor client, okio, [multiplatform settings](https://github.com/russhwolf/multiplatform-settings)) already do that. So I guess it’s as simple as you described? 🙂

@kpgalligan / @russhwolf I’m playing with the

kpg/ktor_refactor

branch but I’ve found the Android version seems to deadlock and never exit the

network

block’s

coroutineScope

, but the

withContext(childContext())

block does return - anything I can do to help debug this?

I have trouble to make the kampkit app run on mac

I noticed that in Android Koin is initialized in the MainApplication, but in iOS this happens in the ViewController, right?

let log = KoinIOS().get(objCClass: Kermit.self, parameter: "ViewController") as! Kermit

Does this mean that each ViewController creates a new DI Container?

No. The init happens here: https://github.com/touchlab/KaMPKit/blob/master/shared/src/iosMain/kotlin/co/touchlab/kampstarter/KoinIOS.kt#L29

It does init in AppDelegate https://github.com/touchlab/KaMPKit/blob/master/ios/KaMPStarteriOS/AppDelegate.swift#L16

We should maybe adjust it to make that more clear, though

No, that’s getting the log, not initing. That mau trigger the init, but it’s not doing it explicitly.

Oh I see the distinction. Yeah we should make that explicit

I really think getting stuff from Koin in Swift, if that’s a thing we want to do, should have an easier path. Maybe some Swift extensions.

Are there any examples on embedding resources in the shared library? I have an ML model I'd like to embed and access in the native code from each platform.

there is something I don’t quite understand about the expect/actual

here you can get the “expect” definition of “network”: https://github.com/touchlab/KaMPKit/blob/master/shared/src/commonMain/kotlin/co/touchlab/kampkit/ktor/DogApiImpl.kt

but I only see the “actual” definition once, for iOS

which is here:

Hello everyone I try to use KmmBridge to build an XCFramework in release but in the documentation I only found spmDevBuild (which is not build the release)