Hello, I created an issue to add inject for Screen in order to work with Android Auto without doing workarounds. What do you think ?

Hi @atlantis210 any problem using

KoinComponent

? is there any missing API ?

Hi, the thing is I had to override screens :

abstract class MyScreen(carContext: CarContext): Screen(carContext), KoinComponent

whereas Screen has lifecycle and add a function for settings the carContext as you did for the Android Context

fun KoinApplication.carContext(carContext: CarContext): KoinApplication {
    if (KoinApplication.logger.isAt(<http://Level.INFO|Level.INFO>)) {
        <http://KoinApplication.logger.info|KoinApplication.logger.info>("[init] declare CarContext")
    }

    koin.rootScope.beanRegistry.findDefinition(clazz = CarContext::class) ?:
        koin.rootScope.beanRegistry.saveDefinition(DefinitionFactory.createSingle { carContext })

    return this
}

and also

fun Scope.carContext(): CarContext = try {
    get()
} catch (e: Exception) {
    throw MissingAndroidContextException("$e")
}

So if this could be inside a library koin-android-auto or something like that, I think it would be easier for other people to continue using koin when on Android Auto

could you set it up in the Koin start sequence, like

androidContext()

DSL keyword

Unfortunately no. The thing is, the

CarContext

has to be set only when connected to Android Auto. And when unplugged the

Context

has to be back to the standard Android Context.

does this car context survive along your application?

It seems it has the same lifecycle as the Android Auto application. The documentation is not clear about it

perhaps this is something you can declare dynamically with

koin.declare()

API

I'm testing it but I'll still have to override the

Screen

component to implements KoinComponent with it whereas it has a lifecycle

I’ll still have to do 

koin.rootScope.beanRegistry.findDefinition(clazz = CarContext::class) ?: koin.declare(carContext)

check the

declare()

function from Koin. You can declare things on the fly

You'll have to add this

implementation '<http://androidx.car.app:app:1.0.0-beta01|androidx.car.app:app:1.0.0-beta01>'

And yes, there is no ViewModel in Android Auto since there is no layouts nor views

apart if you need Android Scope API, then KoinComponent can suits you for now

"check the 

declare()

  function from Koin. You can declare things on the fly and specify `override=true`". I could do that but that's not ideal

cool 👍

anyway, that's a great library you did

if there is a need, it will be more a koin-android-auto for isolating those API 🙂

Yep I agree