6

When I enable the Jack compiler in Android Studio 2.2 the Dagger 2 component is not generated. Can Dagger 2 be used with Jack? If so, how would I go about configuring my application?

From my application's build.gradle:

jackOptions {
     enabled true
   }

 compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
}
David Rawson
  • 20,912
  • 7
  • 88
  • 124
Mario Dennis
  • 2,986
  • 13
  • 35
  • 50

3 Answers3

8

I sunk like 2 days into figuring this out. So I'm circling back to posting the findings here in case it saves someone time:

This is caused by a bug in Jack that prevents classpaths from working properly. It has to do with Jack running "in-process" (in the same JVM as the gradle daemon). Setting android.defaultConfig.jackOptions.jackInProcess to false does get beyond the "Preconditions" error but it causes other problems (2 JVMs that hog system resources) & bugs that break the build in other (worse) ways.

For now, the best solution seems to be:

  • Wait for the 2.3 release of the Android gradle plugin, which already has the fix for this.
  • Downgrade Dagger to v2.2, in the meantime.
    It's the highest version that seems to avoid the Guava conflict with Jack.

EDIT: update 1/14/2017:
I ran into several OTHER problems with Jack and got so tired of it that I switched to retrolambda and kicked myself for not doing this earlier! Right now, Jack simply seems to cause more problems than it solves. Just add the lines with a plus and delete the lines with a minus and you can return to Dagger 2.8 while waiting for Jack to get it's act together!

+plugins {
+    id "me.tatarka.retrolambda" version "3.4.0"
+}

 apply plugin: 'com.android.application'
+apply plugin: 'me.tatarka.retrolambda'

-        jackOptions {
-            enabled true
-        }

For even faster retrolambda builds, add org.gradle.jvmargs=-Xmx4608M to your gradle.properties file so that dexing can happen in-process. Now, I'm on Dagger 2.8 and my clean builds are only 12 seconds, GOOD RIDDANCE, JACK!

Community
  • 1
  • 1
gMale
  • 17,147
  • 17
  • 91
  • 116
3

The documentation page on Jack and Jill has instructions specific to annotation processors "to be applied at compile time but not to be included in your APK", advising the use of the annotationProcessor dependency scope. The example coincidentally mentions Dagger 2:

dependencies {
    compile 'com.google.dagger:dagger:2.0'
    annotationProcessor 'com.google.dagger:dagger-compiler:2.0'
}
Jeff Bowman
  • 90,959
  • 16
  • 217
  • 251
  • 3
    I'm getting the following error Error:Execution failed for task ':app:transformJackWithJackForDebug'. > com.android.jack.ir.JNodeInternalError: java.lang.Exception: java.lang.NoSuchMethodError: com.google.common.base.Preconditions.checkState(ZLjava/lang/String;Ljava/lang/Object;Ljava/lang/Object;Ljava/lang/Object;)V – Mario Dennis Dec 01 '16 at 14:30
  • @Mario That's a problem with mismatched copies of Guava on the classpath. One possibility I hadn't looked into is that Dagger has advanced quite a bit past 2.0, so `2.8` or `2.x` may work much better. – Jeff Bowman Dec 01 '16 at 16:43
  • I'm using version 2.8 – Mario Dennis Dec 01 '16 at 16:59
  • 1
    Got the exact same error as @MarioDennis, using 2.8 as well, and have the same problem if I try using earlier versions. – Adam Honoré Dec 01 '16 at 17:58
  • 1
    For Dagger 2.8 add `classpath 'com.google.guava:guava:20.0'`to your buildscript dependencies. – Avi Cherry Dec 17 '16 at 12:19
  • I also have the same issues as @MarioDennis and it's not resolved by excluding/including dependencies because it's related to a bug in Jack. I posted details in my answer, below. – gMale Jan 12 '17 at 09:23
0

Jack is now deprecated, see this post.

You have to upgrade your Android Studio to 3.0 preview 1, to be able to use Java 8.

If you can't upgrade it (conflict with other lib), or you want to wait for a release version, you can try this workaround solution :

Badr Yousfi
  • 215
  • 3
  • 9