Test code cannot access internal functions in same module

While trying to upgrade to Dagger 2.31.2 I noticed that some of my tests failed to compile saying that the functions they were testing were not accessible because they are internal. After some experimentation I concluded that enableExperimentalClasspathAggregation was the culprit. If I enable it my tests fail to compile, if I leave it disabled they compile just fine.

I’m assuming this has something to do with how that is implemented and I’m guessing it tweaks kapt or something like that.

The module in question is an android library module and I’m using the following dagger/kapt options:

kapt {
  useBuildCache = true
  correctErrorTypes = true

  arguments {
    arg("dagger.fastInit", "enabled")
    arg("dagger.validateTransitiveComponentDependencies", "DISABLED")
  }
}

hilt {
  enableExperimentalClasspathAggregation = true
}

android {
  lintOptions.isCheckReleaseBuilds = false
}

[ansman]

I can confirm it’s working using a snapshot build off master 👏

[sergeys-opera]

I face the same issue with enableExperimentalClasspathAggregation = true. It also breaks :app:lintRelease:

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':app:lintRelease'.
> Could not resolve all files for configuration ':app:debugUnitTestRuntimeClasspath'.