Task ...AndroidTestClassesForKeeper uses output of task ...testFixturesJar without delcaring an explicit dependency

[lwasyl]

Keeper version: 0.13.0 (0.12.0 works fine), AGP 7.4.2

After upgrading to Keeper 0.13.0 I started seeing failures as in the title:

* What went wrong:
Some problems were found with the configuration of task ':app:jarStageReleaseTestAndroidTestClassesForKeeper' (type 'AndroidTestVariantClasspathJar').
  - Gradle detected a problem with the following location: '/<project_path>/feature/foo/domain/build/libs/domain-test-fixtures.jar'.

    Reason: Task ':app:jarStageReleaseTestAndroidTestClassesForKeeper' uses this output of task ':feature:foo:domain:testFixturesJar' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.

    Possible solutions:
      1. Declare task ':feature:foo:domain:testFixturesJar' as an input of ':app:jarStageReleaseTestAndroidTestClassesForKeeper'.
      2. Declare an explicit dependency on ':feature:foo:domain:testFixturesJar' from ':app:jarStageReleaseTestAndroidTestClassesForKeeper' using Task#dependsOn.
      3. Declare an explicit dependency on ':feature:foo:domain:testFixturesJar' from ':app:jarStageReleaseTestAndroidTestClassesForKeeper' using Task#mustRunAfter.

    Please refer to https://docs.gradle.org/8.0.2/userguide/validation_problems.html#implicit_dependency for more details about this problem.
  - Gradle detected a problem with the following location: '/<project_path>/feature/components/bar/domain/build/libs/domain-test-fixtures.jar'.

    Reason: Task ':app:jarStageReleaseTestAndroidTestClassesForKeeper' uses this output of task ':feature:components:bar:domain:testFixturesJar' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.

    Possible solutions:
      1. Declare task ':feature:components:bar:domain:testFixturesJar' as an input of ':app:jarStageReleaseTestAndroidTestClassesForKeeper'.
      2. Declare an explicit dependency on ':feature:components:bar:domain:testFixturesJar' from ':app:jarStageReleaseTestAndroidTestClassesForKeeper' using Task#dependsOn.
      3. Declare an explicit dependency on ':feature:components:bar:domain:testFixturesJar' from ':app:jarStageReleaseTestAndroidTestClassesForKeeper' using Task#mustRunAfter.

    Please refer to https://docs.gradle.org/8.0.2/userguide/validation_problems.html#implicit_dependency for more details about this problem.

There's about 10 of these failures in total, for different modules. I have two workarounds:

• add explicit dependencies in the app module to the offending modules test fixtures
• make the dependencies to offending modules api and not implementation in some other modules on which app depends

Not going into details because as you can imagine, there's lots of various dependencies everywhere — I can share more private details like :dependencies output on Slack. I also tried creating a simple repro with just some transitive modules and test fixtures without success.

I should note that some of the offending modules don't even have testFixtures sources.

So, at this point I'm mostly asking if this looks like something obvious from your end — it feels like since the app compiles without issues, Keeper should be able to do its magic as well. Or maybe you have a hunch about what could be the culprit here so I have a more concrete steps to try to reproduce this in a sample project.

Thanks!