I don’t want different classifier, I wanna be able to do both:

get<MyClass>()
get<MyClass> { parametersOf(MyParams(...)) }

I am testing a module where the top level has parameters. I use checkModules with parameters, but the test only seems to pass some times, most times i get an error that it "Can't get parameter value #0". The following is a sample with the same issue. Anyone who can tell if I'm using it wrong?

import org.junit.experimental.categories.Category
import org.junit.jupiter.api.Test
import org.koin.core.parameter.parametersOf
import org.koin.dsl.module
import org.koin.test.AutoCloseKoinTest
import org.koin.test.category.CheckModuleTest
import org.koin.test.check.checkModules

interface First
class FirstImpl(a: String) : First

interface Second
class SecondImpl(a: First) : Second

@Category(CheckModuleTest::class)
internal class KoinTest : AutoCloseKoinTest() {

    @Test
    fun checkModules() {
        val testModule = module {
            single<Second> { SecondImpl(get()) }
            single<First> { (foo: String) -> FirstImpl(foo) }
        }

        checkModules(parameters = { create<First> { parametersOf("hello") } }) {
            modules(testModule)
        }
    }
}

This message was deleted.

Hello Everyone, We are thinking of upgrading to Kotlin 1.4. Currently our app fails unless we use the version

2.2.0-alpha-1

of koin. Is there any visibility as to when a proper release of 2.2.0 will be available?

Looking into 2.2.0-beta-1 and trying to achieve the same result I had with 2.1.6. Seeing the following issue using new

ScopeActivity

and

ScopeFragment

API’s… • While using shared instance for activity and share it to all the fragments, it is not clear how to instantiate

sharedViewModel

inside fragments that was created by activity. Looks like this API is not available anymore. I was able to achieve same result by using

scopeActivity?.let {
    viewModel = it.getViewModel<SomeViewModel>()
}
is that the way to do this now?

• Another pain point is to inject instances using

scopeActivity

into lazy properties. They are became nullable by default. Is it might be possible to use Fragment’s

requireActivity()

method for getting

requireScopeActivity

which is not nullable. Otherwise I have to insert

?

everywhere in my code then using property initialized like this

protected val imm by lazy {
    scopeActivity?.get<InputMethodManager> {
        parametersOf(requireActivity())
    }
}

• In order to instantiate something that do not require scope from

ScopeActivity

or

ScopeFragment

should I use

GlobalContext

or

ScopeActivity.koin

calls? It is a bit confusing that default

get

or

inject

in

ScopeActivity

and

ScopeFragment

subclasses are trying to get instance from its

scope

. From what I have, usually I’m getting some factory instances by default without any

scope

and some specific (more like a rare) scoped injections. I would prefer to have

scope.get

/

scope.inject

and default

get

/

inject

to be

koin.get

koin.inject

. Not sure might be thats only my opinion and other developers are using it opposite. Fill free to open discussion and drop your comments. I would happy to hear any suggestions or ways to use Koin

scope

system or

sharedViewModel

definition. Thanks!

Koin MP

3.0.0-alpha-3

is out 👍

metadata fixed in

3.0.0-alpha-4

Do you know when there will be available an alpha with the compose branch?

Hello, I am trying to parallelize our unit tests. I am finding that koin is not really designed to be run in a multi-threaded environment. We want to run tests in parallel and each test needs to create it’s own instance of the application and tear it down at the end of each test. Is there any examples of anyone doing this?

Curious if anyone has any thoughts about this https://proandroiddev.com/getting-rid-of-koin-or-how-i-never-learnt-to-stop-worrying-and-love-the-dependency-injection-ee8fe0f4081d

I have some Android instrumentation tests and a dependency declared in a module. In most of our tests, we want the normal dependency. But in one test file, we want to inject a mock version of the dependency. What's the best way to inject a mock dependency and then make sure to replace it with the normal dependency after the tests in that file are complete?

I’m having issue with

override val scope: Scope by lazy { koin.createScope(scopeID, getScopeName(), this) }

in my child fragment which extends from

ScopeFragment

. For some reason it gives me else condition and exception

NoScopeDefFoundException

from

onViewCreated

method.

val scopeDefinition = _scopeDefinitions[qualifier.value]
        return if (scopeDefinition != null) {
            val createdScope: Scope = createScope(scopeId, scopeDefinition, source)
            _scopes[scopeId] = createdScope
            createdScope
        } else {
            throw NoScopeDefFoundException("No Scope Definition found for qualifer '${qualifier.value}'")
        }

Should I declare each fragment scope in my module before I can use or why I could get this error in

2.2.0-beta-1

version? Also it seem to call

createScope

and fail in

onViewCreated

because of this line

koin._logger.debug("Open fragment scope: $scope")

in

ScopeFragment

Update: after a bit of tries. If I declare scope for a fragment like this

scope(named<ChildFragment>()) {  }

It still not work, but I remember it was mentioned that empty declarations will not be allowed… so it works it I declare something scoped

scope(named<ChildFragment>()) {
    scoped { (activity: BaseActivity) -> CustomTabsHelper(activity) }
}

But this is very weird that I have to declare scope before the fragment

createScope

. My assumption was that each

ScopeFragment

is able to create its own scope and I can use that scope anytime I need it. Since all my fragment as extended from the same BaseFragment or similar. This is very unusable since I can’t extend from

ScopeFragment

only on some of them. From other hand declaring useless scopes in modules for each and every fragment I have this is even more work. Not sure what was the idea behind this change. With lifecycle it was much easier (like is it if you need it or just skip it). As usual any feedback or discussions are welcome 😄 Koin is the best anyway 🤟

not sure if this belongs here, but I’ve created a new project with kotlin 1.4 and pasted the gradle file that I used with 1.3.72 and I have this error only on the koin library.. what can be the cause? This is a multiplatform project

Koin 2.2.0-beta-2 is published - https://github.com/InsertKoinIO/koin/blob/master/CHANGELOG.md#220-beta-2

If I would have a

MainActivity

that implements

MainActivityInteraction

interface, and many fragments need this interface in order to communicated with the

MainActivity

, using koins

fragmentFactory

, is that achievable? I cannot actually do:

single {MainActivity()} binds arrayOf(MainActivityInteractions::class)
fragment {BlaBlaFragment(get())} // should get the interface above

Because it's dangerous. Short question, how can I achieve interface communication between fragments and a single activity with koin

Hello fellow koiners 👋 This is regarding multiplatform, as anyone managed to do constructor injection on the Swift/iOS part? So for my specific use case, I want to inject a executor/usecase into a Swift class. The issue is this executor has a dependency and so on and forth, on Android is quite simple as we just need to declare the modules and use

by viewModel()

or wtv it suits you, you could even

inject()

but on Swift seems like we don't have access to Koin's sugar. -- Summarising: View wants to create a ViewModel <- UseCase <- Repository <- RemoteApi Note: '<-' Depends on

Hi there! I think I just found a concurrency issue in Koin. After a few weeks hunting a crash we were having in production, I found out that Koin was sometimes creating more than one instance of a dependency declared as

single

. I've isolated the issue to a concurrency bug in

SingleInstanceFactory

. I have an (ugly) test reproducing it, and a possible solution. It's tricky because the probability of happening is very low, but it happens ^^' @arnaud.giuliani would you like me to open a PR? Or do you prefer to discuss it here before?

Guys,  I had started a library last year to have a wrapper over Jackson for a type safe programming. Please have. a look at it, remarks are highly appreciated and. if you believe it can. be taken further please help to contribute or give it a star if you like it. https://github.com/sahlone/kson

Hi, Is there a way to inject directly into UIViewController classes?

How does Koin compare to Kodein or kotlin-inject in Multiplatform projects currently? Are there any notable limits/restrictions to any one of them?

Anyone having issues with injecting into `@Composable`s? Using

koin 2.2.0-rc-2

with

kotlin 1.4.10

. More details in thread

I’ve added the android name in the manifest and now getting errors that

Unable to start activity ComponentInfo{com.example.cakesapimvvm/com.example.cakesapimvvm.MainActivity}: org.koin.core.error.InstanceCreationException: Could not create instance for [Factory:'com.example.cakesapimvvm.viewmodel.CakeListViewModel']

while waiting for the 2.2.0 stable release, here are some notes about this new release: https://medium.com/koin-developers/whats-next-with-koin-2-2-3-0-releases-6c5464ae5e3d

Anyone used

getViewModel()

in a composable, where the parameters of the vm are subject to change?

Hey guys, I’m writing a functional tests in ktor. One of the suites works absolutely fine and the other one fails to start when `

withTestApplication({ module() }) {

is executed. The error is:

No definition found for class:'com.alpha.CoolService'. Check your definitions!

org.koin.core.error.NoBeanDefFoundException

The bean is definitely there. As I mentioned it works fine in the other test suite. When I stopped there with the debugger there were no beans to be found indeed.

CoolService

is just the first been that I try to retrieve with

get()

. It seems that the context is somehow screwed up. Could it be that the separate ktor test suites are messing up each others Koin contexts?

I've a small question: Is this the correct workaround for compose not yet being implemented in 3.0.0-alpha-4:

@Composable
inline fun <reified T : ViewModel> viewModel(
    qualifier: Qualifier? = null,
    noinline parameters: ParametersDefinition? = null
): Lazy<T> {
    val owner = ViewModelStoreOwnerAmbient.current.viewModelStore
    return remember {
        KoinContextHandler.get().getViewModel(
            owner = { owner },
            qualifier = qualifier,
            parameters = parameters
        )
    }
}

Trying to implement Koin unsuccessfully. Getting the following error. I’ve uncommented a line in the fragment

binding.viewmodel = viewModel

where previously the error was Koin not correctly configured.

The only way to get the current activity context is using parameters when it is being injected?