This message was deleted.

Do you have subprojects with the same name? (For example, if you had

:alpha-modules:foo

and

:blah:test:foo

there are two subprojects are named

foo

. https://github.com/gradle/gradle/issues/847

yes, we have a pattern for subprojects that they're either: •

:library:foo:public

•

:library:bar:public

•

:feature:baz:public

•

:feature:foo:public

• etc.

I have no idea if it's related, but sometimes Gradle gets confused if the group + name of two subprojects are the same. You could quickly try this workaround to make the group of all subprojects distinct: https://github.com/gradle/gradle/issues/847#issuecomment-1159365667

Thanks for the feedback! My issue might be slightly different. We aren't running into circular dependencies on our builds

Hi Ivan, if the module is not reachable from the

app

module, what type of task makes run the isolated module?

Hey Iñaki! in our most recent case the build failed for task

:app:processDebugResources

no tasks for the new module ran