and always deal with it

When this has an application level scope, would it be possible to create the scope on start and then just close/re-create it whenever needed?

you can

it’s like your dealing with one instance only for a particular scope

it’s a usual pattern as we have some http client stack that has to be drop later

in contrary to Koin 1.0 with drop feature, now Koin ensure that single are real singleton and will stay for your container life

scope give you the hand of the timelife of your components, up to you to drop/create this space when you want

but it’s interesting that some people are still using the old approach from Koin 0.9.x 🙂

it deserves a quick help on this topic

If you could give an example, in the docs, like the one you described with the http client stack, it would be perfect!

yep

Hey @arnaud.giuliani ... I'm still waiting for 2.0 stable version and more samples for room. Hope you can release soon 🙂

@Chainchelliah I need time to finish doc, website, some last fixes ...

not easy currently 😕

sorry I will push a beta version

@arnaud.giuliani Yep... Understood.. Thanks 👍

Koin 2.0.0-beta-1 deployed

fragment factory extensions will come in one next beta version 👍

why am I not able to pass

this

to

observe()

when inside an Activity?

works fine with fragments, same viewmodel im trying to inject

same observe calls

it’s not seeing the activity as a lifecycleowner

hm, reverting back to androidx 1.0.1 solved it, even removed the need for the activity to inherit from LifeCycleOwner, as it obviously is

looking at the

KoinContext

code it seems that it only clears all collections of

instances

scopes

and

properties

```

Hi! Today we solved a problem with espresso tests but I don't understand why. Let me explain the situation before solving it, we had an appModule that was providing the context like this:

val appModule = module {	
  single { get<Context>() as InitApp }	
}

And then a dependency that requires the context was satisfied like this:

single { DependencyContext(get<Context>()) }
single { AnotherDependencyContext(get()) } // get() refers to Context

I don't know if it's important but in some places context was satisfied with casting and in another places without casting. The problem was that Espresso tests were failing because

AnotherDependencyContext

could not be satisfied. The solution is change every

get<Context>()

and

get()

(referring to Context) by

androidContext()

and stop providing Context through

appModule

. Do you know why?

@smassive you dont need to expose your Context instance, as it is registered by Koin as

Context

here, as I see it, you force the

InitApp

instance reference

maybe the problem is that cast? Context to InitApp?