Build: AI-202.7660.26.42.7322048, 202104290118,

AI-202.7660.26.42.7322048, JRE 11.0.8+10-b944.6916264x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.16, screens 3440x1440

AS: 4.2; Kotlin plugin: 202-1.4.32-release-AS8194.7; Android Gradle Plugin: (plugin information not found); Gradle: 6.8.3; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: 3.19.3

IMPORTANT: Please read https://developer.android.com/studio/report-bugs.html carefully and supply all required information.

We have a structure roughly as follows:

// :app
dependencies {
  androidTestImplementation project(':test-utils')
}

// :test-utils
src/main/java/Impl.kt
src/main/java/ObserverFix.java

Where ObserverFix.java is an interface:

interface ObserverFix<T> extends Observer<T> {
  @Override void onNext(@Nullable T t);
}

and Impl.kt has

  ...

  private inner class ObserverProxy(
    private val originalObserver: Observer<Any>
  ) : ObserverFix<Any>, Observer<Any> by originalObserver {
    override fun onSubscribe(d: Disposable) {
      DelegateDisposable(d).run {
        addDisposables(this, originalObserver)
        originalObserver.onSubscribe(this)
      }
    }
  }

If I run this incantation with AGP 4.1.3:

./gradlew :app:assembleDebugAndroidTest

and then I inspect the resultant apk with apktool like

apktool d path/to/app-debug-androidTest.apk

I can see that both Impl and ObserverFix are in the apk. If I run the Gradle incantation again with 4.2.0, then only ObserverFix is in the apk -- Impl is nowhere to be found (and the test fails at runtime).

If I remove ObserverFix and make Impl compilable, and then run Gradle again with AGP 4.2.0, then Impl is in the APK again.

So, my suspicion is that this has something to do with the mixed source set, but it's just speculation.

Finally, one of my colleagues was able to figure out which version of 4.2 produced the issue. He tells me that he cannot reproduce this issue with 4.2.0-alpha07, but can repro it with 4.2.0-alpha08. The diff, unfortunately, is huge.

Issue 187353303

Links (5)

Issue metadata