Hi, I'm trying to fix firebase app distribution gradle plugin

tasks.named("appDistributionUpload${variant.name.capitalize()}").configure {
    artifactPath = output.outputFile.absolutePath
    serviceCredentialsFile = project.file("...").absolutePath
    groups = ...
}

this works for modifying the already registered tasks by plugin, but for my setup, I need to register such tasks myself because plugin doesn't generate all it's supposed to (apk splits) so googling gets me this

tasks.register("appDistributionUpload${abiName.capitalize()}${variant.name.capitalize()}", com.google.firebase.appdistribution.gradle.UploadDistributionTask) {
    artifactPath = output.outputFile.absolutePath
    serviceCredentialsFile = project.file("...").absolutePath
    releaseNotes = abi
}

but gradle complains about

A problem occurred evaluating project ':app'.
> Could not get unknown property 'com' for project ':app' of type org.gradle.api.Project.

so I presume the

com.google.firebase.appdistribution.gradle.UploadDistributionTask

doesnt exist is there a way to know the correct fully qualified name of the task if I know its name? printing

this

in the

.configure { .. }

just gives me nonsense 😕

That could also be a Groovy DSL quirk. Sometimes it does not work if you use FQCN, try to use an import instead. Or even better, switch to Kotlin DSL. 🙂 And for thow to get the type,

gw help --task myTaskName

shows information about the task, its supported CLI arguments and also its type.

btw since you're here, do you have any intuition about the related issue i'm seeing? what I'm actually doing now was working in the past, but after I upgraded to latest plugin version the fully qualified name broke, hence me trying to patch it now but, when it was working (i.e. I could call the gradle task via terminal no problem), but in the IDE (Android studio) it sometimes gave me cryptic errors about not knowing the qualified name on IDE sync (yet the task executing worked) is that the quirk you're referring to?

No, doesn't ring any bell.

I see.. I'm not a huge fan of kotlin in gradle, it's slower from what I recall & only really helpful once in a blue moon debugging session like this

I see.. I'm not a huge fan of kotlin in gradle, it's slower from what I recall & only really helpful once in a blue moon debugging session like this

Yeeeah, ..., no. In some situations Groovy is faster, in some situations Kotlin is faster. But the advantages of Kotlin DSL almost always outweigh it majorly. By now it is the default DSL, you immediately get typesafe build scripts, actually helpful error message if you mess up the syntax, and amazingly better IDE support when using a good IDE like IntelliJ IDEA or Android Studio. But hey, to each his tool and sacrifice. 🙂

I love kotlin but I think the way for gradle to go is the declarative route, atleast for me

All these things are in the subclass with the

_Decorated

suffix

okay so you say I should not subclass the "_Decorated"

And well, I don't think it is "the way to go", it mainly is a different DSL

not sure what the correct terminology is .. register by subclassing?

No, register is registering

gotcha

But you cannot access the

..._Decorated

anyway, it it just a runtime decoration of the original class to do the Gradle magic.

btw any idea why the default dsl is like this

firebaseAppDistribution {
    serviceCredentialsFile = file("...") <--------
}

yet when I register

tasks.register("appDistributionUpload${abiName.capitalize()}${variant.name.capitalize()}", com.google.firebase.appdistribution.gradle.tasks.UploadDistributionTask) {
                    serviceCredentialsFile = project.file("....").absolutePath

it forces me to add the

.absolutePath

to make it work?

No, I have no idea of firebase or Android development at all

nobody does even they don't lol but you'd expect the dsl = extension, to be just sugar for getting the input values from user and registering a task like I do, no?

Maybe, maybe not, I have no idea what they are doing and my crystal ball is in the repair shop, sorry 🙂

nevermind thank you anyways!

But digging out my spare ball, the plugin does call

UploadDistributionTaskConfigurator.configure

with the task and extension as arguments and that method does call

task.serviceCredentialsFile.set(nullOrAbsolutePath(extension.serviceCredentialsFile, project))

, so, ...

so I'm doing it right, thanks!

Yeah, well, I'm not interested yet in firebase or android dev, sorry 🙂

worth a shot, thanks 😄

Sure, decompiled by IntelliJ 🙂

yay groovy does it too 😄

Maybe. At least method breakpoints should work, line breakpoints might

and then how do I run it in debug?

Press debug?

ehm..I'm calling

./gradlew ..

pressing debug executes my current IDE run config..no?

Which would be a Grand run config if you run Gradle through the IDE, not command line. So then either run through IDE, for example in the tool window, from the Shift-Shift Run anything dialog. There you can also directly use Shift-Enter to debug instead of run right away. Or if you prefer running from command line, add

-Dorg.gradle.debug=true

and then attach the debugger to 5005