Firebase Crashlytics Gradle Plugins become unresolved after migrating to versions.properties

[mochadwi]

• I have read the guidelines for submitting issues

🐛 Describe the bug

Really not sure if this is firebase-crashlytics-gradle issue or refreshVersions, before adding the refreshVersions, we were able to use any gradle API from firebase-crashlytics-gradle.

⚠️ Current behavior

✅ Expected behavior

The refreshVersions able to coexist with firebase-crashlytics-gradle

💣 Steps to reproduce

Not sure what/which information to provide here, but here's my config:

// versions.properties
version.firebase-crashlytics-gradle=2.7.1

// app/build.gradle.kts
plugins {
    // ... omitted
    id("com.google.firebase.crashlytics")
}

// buildSrc/settings.gradle.kts
pluginManagement {
    plugins {
        id("de.fayard.refreshVersions") version "0.11.0"
    }
}

plugins {
    id("de.fayard.refreshVersions")
}

// settings.gradle.kts
plugins {
    id("de.fayard.refreshVersions") version "0.11.0"
}

📱 Tech info

• Build Scan URL:

[LouisCAD]

You need to use the no-BoM variant.

Unfortunately, the issue is that the Firebase BoM used to include the Gradle plugin, but no longer does.

We have a plan to improve our dependency notations so that the default is the working one.

[mochadwi]

You need to use the no-BoM variant.

Unfortunately, the issue is that the Firebase BoM used to include the Gradle plugin, but no longer does.

We have a plan to improve our dependency notations so that the default is the working one.

Ahhh, noted, yes, we're currently using BoM for Firebase, well noted then, will use the no-BoM a workaround for this, will gives you updates 🙏

[mochadwi]

You need to use the no-BoM variant.
Unfortunately, the issue is that the Firebase BoM used to include the Gradle plugin, but no longer does.
We have a plan to improve our dependency notations so that the default is the working one.

Ahhh, noted, yes, we're currently using BoM for Firebase, well noted then, will use the no-BoM a workaround for this, will gives you updates 🙏

This is so unfortunate, after using the no-BoM variant, the firebase plugin still fails to resolve 🙏

[LouisCAD]

You have a clash between your dependencies and the ones from refreshVersions.

The Firebase object from refreshVersions is used and uses camelCase, not snake_case.

[LouisCAD]

@jmfayard Can we make buildSrcLibs avoid clashes like that one?

[mochadwi]

You need to use the no-BoM variant.

Unfortunately, the issue is that the Firebase BoM used to include the Gradle plugin, but no longer does.

We have a plan to improve our dependency notations so that the default is the working one.

Does this issue already opened, or should I create a feature request for this one?

[mochadwi]

You have a clash between your dependencies and the ones from refreshVersions.

The Firebase object from refreshVersions is used and uses camelCase, not snake_case.

We've removed clashed dependencies from our buildSrc, unfortunately the firebase crashlytics plugins still failed to resolved 😭

[LouisCAD]

Next version of refreshVersions will improve bundled Firebase dependency notations. Hopefully, it helps.

In the meantime, just stick to plain hardcoded dependency notations and use the version placeholder (the underscore _).

[mochadwi]

Next version of refreshVersions will improve bundled Firebase dependency notations. Hopefully, it helps.

In the meantime, just stick to plain hardcoded dependency notations and use the version placeholder (the underscore _).

Removing our previous buildSrc/Dependencies.kt and use hardcoded notation & version placeholder, unfortunately failed to resolve as well :(

[LouisCAD]

refreshVersions 0.20.0 is out with updated dependency notations. If it still doesn't work on your end, please link us a minimal reproducing project.

[mochadwi]

android-agentapp.zip here's our private internal project, we also remove everything from credentials and our entire codebase, except the build.gradle(.kts) and a few scripting files

[mochadwi]

android-agentapp.zip here's our private internal project, we also remove everything from credentials and our entire codebase, except the build.gradle(.kts) and a few scripting files

we also updated to the version 0.20.0, there's a little problems for this code (so we commented out for a while):

// implementation(Square.Retrofit2.retrofit) {
    //     exclude(group = "com.squareup.okhttp3")
    //     because("version 3.x pulled from retrofit")
    // }

please let us know if need anything 🙏 thank you ❤️

[LouisCAD]

The issue is that firebaseCrashlytics { … } doesn't exist, because it's not optimized for Kotlin DSL, and I think you migrated from Groovy DSL which can go through runtime hacks to get that working. It's unrelated to refreshVersions itself.

[mochadwi]

The issue is that firebaseCrashlytics { … } doesn't exist, because it's not optimized for Kotlin DSL, and I think you migrated from Groovy DSL which can go through runtime hacks to get that working. It's unrelated to refreshVersions itself.

looks like this is issue on firebase gradle plugins unsupported to GKD (Gradle Kotlin DSL) itself, cmiiw?

[LouisCAD]

BTW, posting big screenshots isn't very helpful to us. Giving the relevant part of the error messages, and any relevant small snippet is much less overwhelming for us, and we can sometimes reply when on mobile, which is hardly doable with these gigantic screenshots.

[mochadwi]

BTW, posting big screenshots isn't very helpful to us. Giving the relevant part of the error messages, and any relevant small snippet is much less overwhelming for us, and we can sometimes reply when on mobile, which is hardly doable with these gigantic screenshots.

well noted, my apologize for the screenshot, I should've resize it before commenting 🙏 :D

because it's not optimized for Kotlin DSL, and I think you migrated from Groovy DSL which can go through runtime hacks to get that working

Thanks again for confirming this 🙏

[LouisCAD]

It supports it, but you cannot configure it the way you're doing. Just search for "firebase crashlytics kotlin dsl" on Google and you'll get the info you need to do what you want.

[mochadwi]

It supports it, but you cannot configure it the way you're doing. Just search for "firebase crashlytics kotlin dsl" on Google and you'll get the info you need to do what you want.

found it! thanks again!

for future readers, see workaround using this:

// app/build.gradle.kts

plugins {
  //...
  id("com.google.firebase.crashlytics")
}

android {
  buildTypes {
    getByName("release") {
      (this as ExtensionAware).configure<CrashlyticsExtension> {
        mappingFileUploadEnabled = true
        nativeSymbolUploadEnabled = true
        // etc.
       }
    }
  }
}

or

// app/build.gradle.kts
import com.google.firebase.crashlytics.buildtools.gradle.CrashlyticsExtension

android {
  buildTypes{
        getByName("release") {
            configure<CrashlyticsExtension> {
                mappingFileUploadEnabled = false          // to disable mapping file uploads (default=true if minifying)
                nativeSymbolUploadEnabled = true         // to enable NDK symbol file uploading (default=false)
                unstrippedNativeLibsDir = "path/to/libs" // optional override to change the default unstripped native library path, only used in NDK builds 
            }
        }
    }
}

ref:

1. Firebase-crashlytics Gradle plugin: kotlin dsl support firebase/firebase-android-sdk#1622 (comment)
2. Unresolved reference to firebaseCrashlytics Gradle extension since 2.6.0 [firebase-crashlytics-gradle] firebase/firebase-android-sdk#2665 (comment)