Dagger not generating Proguard/R8 rules with option experimentalUseStringKeys

I’m having some issues with experimentalUseStringKeys on Android Studio 3.4 (beta 3). When running the app (release build with R8) it throws the following exception:

 java.lang.IllegalArgumentException: No injector factory bound for Class<Alb>

When adding the following to my Proguard rules manually the exception does not occur anymore:

-identifiernamestring class dagger.android.internal.AndroidInjectionKeys {
  java.lang.String of(java.lang.String);
}

So it looks like that for some reason this isn’t added automatically by Dagger, which is strange as I verified that a generated APK used R8 version 1.4.29. This should have support for generated proguard rules.

Android Studio version: 3.4 beta 3 (same issue in 3.3 stable) Dagger version: 2.21

EDIT: Fixed Android Studio version

[ronshapiro]

I opened a bug on R8 here. Let’s converge on that, and we can reopen if that ends up not being the case.

[JakeWharton]

Maybe a bug in the toolchain only assuming it needs to carry class files as outputs?

On Thu, Feb 7, 2019 at 4:55 PM Ron Shapiro [e-mail] wrote:

I’m seeing these files generated:

./app/build/intermediates/javac/release/compileReleaseJavaWithJavac/classes/META-INF/proguard/dagger.android.AndroidInjectionKeys ./app/build/intermediates/javac/debug/compileDebugJavaWithJavac/classes/META-INF/proguard/dagger.android.AndroidInjectionKeys

I’m not sure why R8 is not picking them up.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/google/dagger/issues/1415#issuecomment-461606589, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEEESCuCq5g8TKGuPJp3nE1dgJ0DAvSks5vLKDugaJpZM4ahwxz .