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

Gradle Community

If you think it could be due to cache ,  then perhaps running with `--rerun-tasks` or with build-cache disabled may help confirm that? But this most probably is a convention used by the task/plugin responsible for publishing. What version of AGP and gradle are these?

I’d also expect more support on this in <#CJYS1DAP5|> ..Since android’s artifact publishing is a  can of worms by itself :slightly_smiling_face:

This is for AGP `7.1.2` and Gradle `7.4.2`
---
Rerun tasks and no build cache did not work, will try a nuke nuke option now :cry:

Ah okay..~There were publishing  bugs in AGP prior to 7.2.1~ . Disregard that, 7.1.2 has the fixes.

I’ve successfully created aar artifacts (with much lesser custom code) with AGP 7. I imagine you are creating an aar here?

Are you using the new publishing api ?(<https://developer.android.com/studio/publish-library>) .

So… nuke options works!

Removing `GRADLE_USER_HOME/caches` is not, but removing `GRADLE_USER_HOME/.tmp` is!

I think it’s related to the artifact transform but I’m still not familiar with it.

&gt; Are you using the new publishing api ?
Not yet, but we have this on other branch :smile:

For now, we disable the automatic component generation

Oh..TIL about the `.tmp` directory…what does that contain ?

Not really sure, I check the directory again after build success but the directory is empty. But after deleting that, `detachedConfiguration` starts running again :thinking_face: