Calling Koject.start() multiple times creates dependencies again and again

[srikrishnacj]

Currently we call Koject.start() from MainActivity.onCreate. Each time dark theme is toggled, MainActivity.onCreate being called again and so Kojact.start(). This leads to singleton dependencies created multiple times. currently my workaround is

@SuppressLint("StaticFieldLeak")
object ApplicationContextModule {
    lateinit var context: Context
    var start = false

    @Provides
    fun provideContext(): Context {
        return context
    }
}

ApplicationContextModule.context = this.applicationContext
if (!ApplicationContextModule.start) {
    Koject.start()
    ApplicationContextModule.start = true
}

But it would be nice if framework itself detect these changes

[mori-atsushi]

In android, I recommend calling Koject.start() in your application class.

class MyApplication : Application() {
    override fun onCreate() {
        super.onCreate()

        Koject.start {
            application(this@MyApplication)
        }
    }
}

Please refer to the following documents for details.
https://mori-atsushi.github.io/koject/docs/android/application

[mori-atsushi]

Koject.start resets singleton for testing. This is the expected behavior.