BuildConfig can not be resolved in unit tests when using android.enableBuildConfigAsBytecode=true [363031540]

Fixed

Bug

Status Update

No update yet.

Description

va...@gmail.com

created issue #1

Aug 30, 2024 11:29AM

Reproducer: https://github.com/vanniktech/playground/pull/247

Turn on: android.enableBuildConfigAsBytecode=true and then this test can't be compiled:

class EmptyUnitTest {
  @Test fun empty() {
    assertEquals(true, BuildConfig.DEBUG)
  }
}

Execute ./gradlew testDebug and you will see the compile error:

EmptyUnitTest.kt:8:24 Unresolved reference 'BuildConfig'.

To workaround this in the defaultConfig block I can add the following: buildConfigField("String", "WORKAROUND", "\"foo\"") this will yield a BuildConfig that can be resolved.

Regardless of whether I have buildConfigFields declared or not, when using enableBuildConfigAsBytecode the BuildConfig should be resolvable in the Unit Tests.

Comments

ra...@google.com <ra...@google.com> Sep 4, 2024 02:20AM

Assigned to an...@google.com.

je...@google.com <je...@google.com> Sep 9, 2024 04:04PM

Reassigned to mi...@google.com.

mi...@google.com <mi...@google.com> #2Oct 1, 2024 12:27AM

Marked as fixed.

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Studio Ladybug Feature Drop | 2024.2.2 Canary 3
Android Gradle Plugin 8.8.0-alpha03

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

an...@google.com <an...@google.com> #3Oct 3, 2024 07:49PM