Is there subcomponents or similar to Dagger subcomponents in Koin? I want to be able to create these dependencies subgraph on the fly as the user browse the different sessions of the App. Similar to component dependency in Dagger. What is the closest approach?

Hi @arnaud.giuliani, I used

@Preview

annotations in my function, but I am getting error on design issues message.

This preview was unable to find a CompositionLocal. You might need to define it so it can render correctly. Show Exception

Hi, another question what is difference between

getViewModel()

or

koinViewModel()

in compose function?

I'm new to Koin and ran across something that was unexpected and I'd like to know if I'm either understanding it wrong, or doing it wrong. I've got a dependency declared as

factory { Service() }

, and I'm attempting to use it in a class as a property declared as

val service: Service by inject()

. It works, but it seems that every time I reference that property in my class, Koin creates a new instance. Is that how it's supposed to work? I expected it to construct the

Service

lazily, but after that I'd get the same instance until the parent class is destroyed. Changing

by inject()

to

= get()

gets me the behavior I want, but I really want to know why

by inject()

isn't working as I expect.

Good morning. I’m converting my app to Koin annotations ( 3.2.2 + 1.0.3 ) and I think I found one ( two? ) issue(s). After converting all my modules, I have an “aggregator”, like

@Module(includes = [...])
class MyAppModule {

  // couple of defs here
}

And here’s the first issue: the generated code has syntax issues, like

includes(.SomeModule

( note the

.

before the name and missing qualifier ) Since in the

includes = [...]

I had about 50 modules, I thought I broke the processor, so I grouped them into other modules like

@Module(includes = [A::class, B::class])
class MyAppModule {

  // couple of defs here
}

@Module(includes = [...])
class A

@Module(includes = [...])
class B

But seems like

A

and

B

are not processed, as there is generated code only for

MyAppModule

Can you mix koin-core & koin-android in 3.3.0? Upgrading to 3.3.0 gave me some odd exceptions at runtime with

startKoin

and

androidLogger

import org.koin.android.ext.koin.androidContext
import org.koin.android.ext.koin.androidLogger
import org.koin.core.context.startKoin

class MainApplication : Application() {
    @Suppress("SpreadOperator")
    override fun onCreate() {
        super.onCreate()
        startKoin {
            androidLogger()
            androidContext(this@MainApplication)
            modules(*allModules)
        }
    }
}

java.lang.LinkageError: Method void org.koin.android.logger.AndroidLogger.log(org.koin.core.logger.Level, java.lang.String) overrides final method in class Lorg/koin/core/logger/Logger; (declaration of 'org.koin.android.logger.AndroidLogger'

Hi there 👋 several updates for koin projects: `- koin-core`& `koin-test`updated in 3.3.0 -

koin-android

update in 3.3.1 - `koin-androidx-compose`in 3.4.0 https://github.com/InsertKoinIO/koin/blob/main/CHANGELOG.md

also upates to come for `koin-ktor`and

koin-annotations

A bit of reading about Koin in NowInAndroid app: https://proandroiddev.com/now-in-android-with-koin-part-1-2b871d8549f1

Hi everyone! I’m using a library that, as I can see, has dependencies on koin-android 3.1.6 and also on koin-core 3.1.6. As a limitation on my side, I can only add those dependencies on AAR or JAR files. I have found and added the koin-android AAR and the koin-core JAR, but when I run my app I’m having the following error: “Failed resolution of: Lorg/koin/dsl/KoinApplicationKt” It looks like haven’t found the class KoinApplication that if I’m right, it should be in the koin-core JAR. Does anyone know why it isn’t finding the class KoinApplication? Do I have to use a specific koin-core JAR file? Is there a koin-core AAR version to try?

Why is

koin-ktor

repository archived? Is this module deprecated? How should we use Ktor with new Koin release?

What is the reasoning behind making koin-compose depend on androidx navigation? It brings in the androidx navigation library, even though I'm using a different implementation. I've been staying on a previous version that does not add androidx nav, but then I am losing bug fixes and new features. Could this be fixed?

When I try to use annotations in an Android library I get

Could not determine the dependencies of task ':feature1:extractDebugAnnotations'.
> Could not create task ':feature1:kspDebugKotlin'.
   > Could not create task of type 'KspTaskJvm'.
      > org/jetbrains/kotlin/gradle/dsl/KotlinJvmOptionsImpl

Is there a gradle.build.kts example for the setup? https://insert-koin.io/docs/setup/ka_1.0/ only has the Groovy code like

android {
    applicationVariants.all { variant ->
        variant.sourceSets.java.each {
            it.srcDirs += "build/generated/ksp/${variant.name}/kotlin"
        }
    }
}

Hi there, I've noticed a behavioral change between 3.1.1 and 3.2.1 (which is also present in 3.3.0). It seems that objected are not loaded eagerly anymore. Consider the following example:

import org.koin.dsl.koinApplication
import org.koin.dsl.module

data class Tester(val id:String, val created :Long ){
    init{
        println("creating $this")
    }
}

fun main() {
    val myModule=  module(createdAtStart = true) {
        single(createdAtStart = true){
            Tester("A", System.nanoTime())
        }
    }

    val koinApplication = koinApplication {}
    val koin = koinApplication.koin
    koin.loadModules(modules = listOf(myModule))

    println("everything loaded?")

    println(koin.get<Tester>())
}

The print order changes between the mentioned versions. To me this qualifies as a bug.

Hello! I'm migrating from 3.1.4 -> 3.3.0 Looking at this, does this mean if you are not using androidx-navigation NavBackStackEntry as your ViewModelStoreOwner - we no longer can use these extensions?

Hi, I’m getting this error:

Property delegate must have a 'getValue(Nothing?, KProperty<*>)' method. None of the following functions is suitable: public inline operator fun <T> Lazy<???>.getValue(thisRef: Any?, property: KProperty<*>): ??? defined in kotlin

in this line:

val slackCommandListener by inject<SlackCommandListener>()

My listener is defined in koin as follows:

//in modules.kt
val listenerModule = module {
    factory { SlackCommandListener(get(), get()) }
}

//in koin.kt
install(Koin) {
        slf4jLogger(level = org.koin.core.logger.Level.ERROR)
        modules(serviceModule, controllerModule, listenerModule)
}

Can someone please help? T.I.A.

Hi all. I've recently decided to give koin a go (after tears of using #kodein) ans can't help but wonder what's up with artefact versions being all over the place? Is there koin bom I could pull in to manage them?

is there any way when creating a scope to pass a parameter that we live inside that scope? got an identifier that everything created in that scope needs passed into it. currently I do it with an inject parameter, but it would be nice to clean up all of my injection sites by just having that one common parameter live inside the scope itself

Any recommended way of using Koin with JB Compose in the project with shared UI in shared? Right now, i use my own Injector interface with Impl as KoinComponent, but I wonder if there is an existing Koin solution in place.

Hi, I’m trying to migrate from 3.2.2 to 3.3 in a multiplatform project. A number of

singleOf

declarations in the format below are now unable to be resolved at compile time. How should I be migrating these? I couldn’t seem to find any migration guide or detail of this in the changelog, unless I’ve missed something!

module {
    // ...
	singleOf { a, b, c -> SomeFactory(a, b, c).build() }
}

// Compiler error:
// None of the following functions can be called with the arguments supplied: ...
// public inline fun <reified R> Module.singleOf(...
// etc ...

I’m trying to migrate some code to compose and have come across a scenario where I have a viewmodel defined in an activity with koin and would like to use this inside of a composable within a composeview in this activity. What would be the easiest way of doing this? My old non-migrated fragment used

by activityViewModel<...>()

and i wondered if there is something similar or what i would need to pass to the

getViewModel

composable to get the same result.

What's the best practice for using Koin when creating libraries? I'm just starting to explore Koin and noticed that I need to initialize everything with

startKoin

but libraries don't typically have a main entry point so I'm wondering how to approach DI when creating libraries

I am trying to use annotations in my KMP application, but I have an error that I can't work around. I am using code from HelloWorld-KMP, using the annotations branch. A problem occurred configuring project ':androidApp'.

Could not create task ':androidApp:compileDebugKotlin'.

> Cannot convert the provided notation to a File or URI: [/Users/jamesblack/AndroidStudioProjects/MyPasswordSafe/androidApp/build/generated/ksp/debug/kotlin].

Hi, I try to understand if scope is suitable to what I wanna do, but I can’t make this simple example to work. Can anyone help me making this test run successfully (see thread). Thanks a lot!

Recently I faced a problem with

ViewModel

not working correctly with

Qualifier

. The issue is described here. Is there any workaround I can apply until it’s resolved?

Is there anyone who used Koin annotation in a real KMM project? I’m trying to use it but it does not resolve

org.koin.ksp.generated.module

even in the Koin sample project https://github.com/InsertKoinIO/hello-kmp

Hi all, How do you pass parameters to a scope? I can define like this:

scope(named<Example>()) {
    scoped { params -> Example(name = params.get()) }
}

but how do I resolve the instance in the scope afterwards? Thanks!

Hi people, where I can find koin compose changelog?