any idea?:)

# kodein

[hamutarto]

any idea?:)

[Andreas Sinz]

are you using proguard or something similar?

[hamutarto]

yeah but without any fancy setup

[hamutarto]

do you think proguard is the culprit?

[hamutarto]

I switched it off, same issue 😕

[Andreas Sinz]

yeah, in most of the cases where this error occurs, because proguard replaces unused classes with Object

[Andreas Sinz]

can you show us the code with the bindings?

[hamutarto]

sure

[hamutarto]

class UserProviderImpl() : UserProvider {

    override fun getUser() {
    }

}`

val userProviderModule = Kodein.Module {
    bind<UserProvider>() with singleton { UserProviderImpl() }
}

[hamutarto]

class AssignmentProviderImpl() : AssignmentProvider {

    override fun getAssignments(): List<AssignmentViewModel> {
        return arrayListOf()
    }
}

val assignmentProviderModule = Kodein.Module {
    bind<AssignmentProvider>() with singleton { AssignmentProviderImpl() }
}

[hamutarto]

these are the new ones

[hamutarto]

in my application

[hamutarto]

override val kodein by Kodein.lazy {
        import(analyticsModule)
        import(userProviderModule)
        import(assignmentProviderModule)
        import(apiModule)
    }

[hamutarto]

analytics module has

[hamutarto]

val analyticsModule = Kodein.Module {
    bind<GMAnalytics>() with singleton {
        GMAnalyticsImpl(
            instance()
        )
    }
}

[hamutarto]

and api module has

[hamutarto]

val apiModule = Kodein.Module {
    bind<GMApi>() with singleton { GMApiImpl(GMApiService.create()) }
}

[hamutarto]

If I’m not using the

[hamutarto]

import(userProviderModule)
import(assignmentProviderModule)

[hamutarto]

in the applicaion

[hamutarto]

then everything is fine

[hamutarto]

# Some methods are only called from tests, so make sure the shrinker keeps them.
-keep class com.example.android.architecture.blueprints.** { *; }

-keep class android.support.v4.widget.DrawerLayout { *; }
-keep class android.support.test.espresso.IdlingResource { *; }
-keep class android.support.test.espresso.IdlingRegistry { *; }
-keep class com.google.common.base.Preconditions { *; }
-keep class android.databinding.** { *; }
-keep class android.arch.** { *; }

# For Guava:
-dontwarn javax.annotation.**
-dontwarn javax.inject.**
-dontwarn sun.misc.Unsafe

# Proguard rules that are applied to your test apk/code.
-ignorewarnings

-keepattributes *Annotation*

-dontnote junit.framework.**
-dontnote junit.runner.**

-dontwarn android.test.**
-dontwarn android.support.test.**
-dontwarn org.junit.**
-dontwarn org.hamcrest.**
-dontwarn com.squareup.javawriter.JavaWriter
# Uncomment this if you use Mockito
-dontwarn org.mockito.**

[hamutarto]

this is my proguard

[Andreas Sinz]

please put the code in 3 backticks if its more than a line

[hamutarto]

yeah sorry

[hamutarto]

changed

[hamutarto]

any idea?:(

[hamutarto]

one additional thing

[hamutarto]

I have a baseclass for my activites and for my fragments with the injector codes

[hamutarto]

like

[Andreas Sinz]

I think you are hitting https://github.com/SalomonBrys/Kodein/issues/93

[Andreas Sinz]

does it work if you disable proguard and do a clean build?

[hamutarto]

let me retry

[hamutarto]

wow

[hamutarto]

I injected all of them and used a function from all of them

[hamutarto]

and now it’s working

[hamutarto]

it was definitely proguard

[Andreas Sinz]

Seems like you are missing that statement in your proguard-config too https://salomonbrys.github.io/Kodein/#_using_proguard

[Andreas Sinz]

not sure if its still up-to-date

[hamutarto]

I actually have it

[hamutarto]

so it must be a different one

[Andreas Sinz]

then you could probably tell proguard to keep the classes you are binding with -keep class ...

[hamutarto]

later it shouldn’t be a problem, as these objects will be used. I just kickstarted a new project so there wasn’t any functionality in these objects