Good day, Following are 2 weird behaviors I noticed after 3.1.0 migration… Just things that you need to be consider while declaring your classes in module… 1. Handling default parameters in the constructor are not supported/ not working, so you must declare body explicitly every time you want to declare some class which has

default parameter

. Otherwise you will get

Declaration parameter error

. 2. Second pain point I got is related to the

parametersOf

/

params

and class casting. Especially that causes error if you pass an implementation of the interface, but interface is expected as a parameter for the instance constructor. In this case

params.[get|get<Something>|getOrNull]

will not work, because expected

T::class

isn’t the

parameter::class

. The only way I get it to work is to use

params[0]

. I assume all this could lead to confusion for people and also will take some time without a proper guidance in which case what should be used. Added samples to thread as well for illustration purposes 👀 It could be also that I misunderstood the concept or something… in this case I would appreciate if someone who aware could give highlight for me.

This message was deleted.

HI! Trying to use koin

3.1.0

crashes with:

Process: <http://com.alorma.online|com.alorma.online>, PID: 27063
    java.lang.NoSuchMethodError: No interface method startReplaceableGroup(ILjava/lang/String;)V in class Landroidx/compose/runtime/Composer; or its super classes (declaration of 'androidx.compose.runtime.Composer' appears in /data/app/~~Blc5lbQ6ufp-BTmeiEZj8Q==/com.alorma.online-HU9SyBXOt-tG6CArGrkzLg==/base.apk)

Hi folks. I just upgraded to 3.1.0 and I am noticing something odd. The following code fails to compile

viewModel(override = true) { SearchScreenViewModel(get()) }

I am guessing that the override param was removed from the viewModel call (release notes mention something about it s being a global option). Could someone explain as to what that means and how would we configure something like this in the new system. On a side note the documentation for the function still mentioned override as a accepted param (most likely an oversight) but thought you might want to know 🙂

Hi, where can I find info on using Koin in a KMM project?

Koin 3.1.1 deployed - https://github.com/InsertKoinIO/koin/blob/master/CHANGELOG.md#311

This message was deleted.

Hello 👋 I'm trying to retrieve the arguments in the savedStateHandle from the VM. Apparently argument passed as argument in the navcontroller can be retrieved like this. I've tried to do some thing like in this video However the savedStatehandle is always empty?

Trying to use KoinTest for instrumented compose tests. My test class implements KoinTest and I use KoinTestRule

@get:Rule
val koinTestRule = KoinTestRule.create {
    modules(module)
}

and stopKoin @After

@After
fun stopKoin() {
    stopKoin()
}

however the very first test that is run fails with

java.lang.IllegalStateException: No Koin application found

but the following tests run just fine. What could be the reason for this? 😞

I’m in the process of upgrading from 3.0.1 to 3.1.1, and am getting runtime errors due to

single(createdAtStart = true)

being started more eagerly than in 3.0.1. Now it seems that such declarations are immediately invoked. Is this working as intended (i.e. 3.0.1 was faulty) or a bug in 3.1.1?

I am using Firebase Remote Config and I have created a Wrapper class for use throughout my app, injected via Koin. The Firebase Remote Config singleton requires some initial setup before it can be used. Currently I do this in my Application subclass just before I start Koin, but I was wondering if there was a better way? Can Koin be told to instantiate a class immediately rather than on first use? If so, i can mov the initialization code into init() of the wrapper class.

Hey i am using koin v2.2.2 in my project. In viewmodel parameter i am declare context object , it giving warning. How to prevent this

Hey! Im using Koin

v.3.1

and I have some issue with the injection of the

SavedStateHandle

in my ViewModel When my viewmodel is called for the first time in my Fragment, I received a new SavedStateHandle and not the one I see from the Fragment Does anyone have an idea Here’s the code: VM

class ArticleViewModel(
        private val savedStateHandle: SavedStateHandle,
        private val useCase: ArticleUseCase) : ViewModel() {

AppModule

viewModel { ArticleViewModel(get(), get()) }

I'm having a really hard time figuring out why I get a crash getting a view model. It works the first time but not the 2nd. I am using KoinApplication and not startKoin (as this is a library)

@arnaud.giuliani Hello, could you please take a look into a closed issue? I have reproduced the crash and added the sample project. https://github.com/InsertKoinIO/koin/issues/1095

on multiplatform / js how can i initialize singles with suspend functions ?

Is there a way to link a component (eg:Presenter injected multiple times) to a viewmodel scope ? Edit: in a full compose app

Are there any examples of using Koin in a Jetpack Compose test (as described in https://developer.android.com/codelabs/jetpack-compose-testing) ...for example being able to inject mock dependencies?

Hey! 👋 I’ve seen the way KaMPkit and John O’Reilly’s

People in Space

handle the Koin injection in a multiplatform project and both are pretty cool. But in the long term, you will also need a DI framework for the Swift app. I know this is a long, shot, but is there any way or future plan to include the injection on the iOS app itself using Koin? I mean, not needing another DI framework. This would make Koin super powerful in multiplatform projects. What do you think? Is it possible in any way?

Hi! I got a question about scopes + viewModel. I have two fragments, and for both I have two scopes(smth like

scope(qualifier = named<Fragment1>()) { ... }

Also I want to share one viewModel between them. I found that I need t create one more scope with viewModel and link it with both fragment's scopes. Is it a good practise? Any suggestions how to do this correctly? Also they are not parent and child. It's two different fragment in navigation graph

Is it recommended to replace

GlobalContext.get()

with

KoinPlatformTools.defaultContext().get()

?

is there a way to provide dependencies of the same type and inject them all together as a list? multibindings

I have a component that needs to be shared by various subcomponents within ViewModel, what is the best way to accomplish this? It needs to be the same instance

ViewModel(sharedComponent, OtherComponent(sharedComponent))

Hello, how would I go about binding different implementations based on an environment variable?

Is there a way of having sub applications? For example a root application and multiple sub applications that all inherit instances and modules of the root application.

Hi, I've searched the docs but could not find any lead: How can I use koin from java (for interop reasons I'm using a mixed code repo)?

smthg.getKoin().get(FooBar.class)

does not work because the argument is not a KClass, but I have no clue how to create one from java.

Thoughts on adding a lint warning / compiler warning for instances where

ViewModel

is instantiated via

by inject()

instead of

by viewModel()

?

Hey 👋 Is there any way to scope a

viewModel

to a navigation graph using Jetpack compose navigation? I would like a

viewModel

to be used by several composables and get cleared and reinstantiated when the user exists -> reenters to that screen flow.

Hi I posted some questions on #koin-dev but I just found out about this channel so will post here as well, probably more appropriate: When overriding a module like in the documentation example: val myModuleA = module { single<Service> { ServiceImp() } } val myModuleB = module { single<Service> { TestServiceImp() } } // Will throw an BeanOverrideException startKoin { modules(myModuleA,myModuleB) } we see that koin create ServiceImp instance but even if we override it - any good way to avoid it ? It is a ktor-koin project and we have some scheduler in the ServiceImp init that we don’t want to start at all when just running the tests Thanks