Unresolved reference to firebaseCrashlytics Gradle extension since 2.6.0 [firebase-crashlytics-gradle]

[READ] Step 1: Are you in the right place?

Issues filed here should be about bugs in the code in this repository. If you have a general question, need help debugging, or fall into some other category use one of these other channels:

• For general technical questions, post a question on StackOverflow with the firebase tag.
• For general Firebase discussion, use the firebase-talk google group.
• For help troubleshooting your application that does not fall under one of the above categories, reach out to the personalized Firebase support channel.

[REQUIRED] Step 2: Describe your environment

• Android Studio version: 4.2 (Latest Stable channel)
• Firebase Component: Firebase Crashlytics Gradle plugin
• Component version: 2.6.0+ (started in 2.6.0, still happens in latest 2.6.1)

[REQUIRED] Step 3: Describe the problem

The Gradle configuration to use the ‘firebaseCrashlytics’ Gradle extension, in order to set configuration properties such as ‘mappingFileUploadEnabled’, can no longer be resolved. This is using an unchanged set up that worked in previous version and is the same as what is in the Firebase Android documentation.

Steps to reproduce:

• Add configuration to app module Gradle configuration to use the ‘firebaseCrashlytics’ Gradle extension and set any property, such as ‘mappingFileUploadEnabled’.
• When you configure the project you get Unresolved errors relating to the extension.

e: /src/app/build.gradle.kts:146:13: Unresolved reference: firebaseCrashlytics
e: /src/app/build.gradle.kts:147:17: Unresolved reference: mappingFileUploadEnabled
e: /src/app/build.gradle.kts:164:13: Unresolved reference: firebaseCrashlytics
e: /src/app/build.gradle.kts:165:17: Unresolved reference: mappingFileUploadEnabled

If you rollback to the previous version, 2.5.2, everything works again.

Relevant Code:

In the app module build.gradle.kts:

buildTypes {
    getByName("debug") {
        ...

        firebaseCrashlytics {
            mappingFileUploadEnabled = false
        }
    }
    
	...
}

[lordcodes]

Closing the issue, as the it has been resolved with guidance of what we should be doing. It sounds like the issue of updating Kotlin DSL documentation is also “in hand”.

[mrichards]

@lordcodes @kmayoral In addition to the withGroovyBuilder workaround, I believe use of the Kotlin DSLs ExtensionAware.the() functions will work:

import com.google.firebase.crashlytics.buildtools.gradle.CrashlyticsExtension
// ...
 getByName("debug") {
      // ...
      the<CrashlyticsExtension>().mappingFileUploadEnabled = false
      // or
      the(CrashlyticsExtension::class).mappingFileUploadEnabled = false
}

This is a little less attractive as it exposes the CrashlyticsExtension class in your build script rather than allowing you to use the firebaseCrashlytics block, but it gives better type safety than the withGroovyBuilder workaround. Thoughts on this?

Just be advised that technically CrashlyticsExtension isn’t part of our public API. However, if we break this syntax it will be while adding improved Kotlin support so we’ll be sure to publish official docs describing the preferred approach.

Finally, can either of you confirm that using the firebaseCrashlytics.mappingFileUploadEnabled = false syntax actually worked as expected in a Kotlin build script? In my test apps using 2.5.2, my builds succeed but the value isn’t respected.