From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

The task is probably added after you do that `findByName` which is bad anyway, as it prevents task configuration avoidance.

Better do
```tasks
    .matching { it.name == "kspKotlinIosSimulatorArm64" }
    .configureEach { finalizedBy("myTask") }```

Thank you so much! One last question, imagine that the task is defined in the root:
project:
• gradle &lt; here
• module
    ◦ gradle &lt; called here
is there a way to specify the “path” to the task? Like “../taskName”

```finalizedBy(":myTask")```
I guess.
But that is a bit smelly :slightly_smiling_face:

Nice it worked! Why do you say it’s smelly? :sweat_smile: Let’s say I’ve a module that creates some helper tasks, to call them I must use “:module:task” right?

Well, it sounds smelly that `:module:kspKotlinIosSimulatorArm64` should be finalized by a task in `:`.
Maybe it is ok, but heavily depends on the details, just feels wrong instantly.
And a "module with helper tasks" also does not really sound idiomatic. :smile:

eheh yeah I get your point. Well in my case I’m generating some swift files and I need to copy them after that task. Maybe a big “magic”, buuut, it’s an experiment :upside_down_face: I can provide a link when published.