I have a KMP gradle project with (multi-module, composite build) and more times than not I get a few...

# gradle

[Tóth István Zoltán]

I have a KMP gradle project with (multi-module, composite build) and more times than not I get a few gpg: signing failed: Cannot allocate memory errors when I try to publish the modules. I use com.vanniktech.maven.publish for publishing with the standard signing plugin. If I run publish again a few times it eventually signs everything but it is really distracting to run it 3-4 times to get the modules published. Any pointers how to solve this? The JVM memory passed to the gradle project doesn't matter (makes sense, gpg runs outside the JVM I think). I'm on Mac OS.

signing {
    useGpgCmd()
    sign(publishing.publications)
}

mavenPublishing {

    publishToMavenCentral(SonatypeHost.CENTRAL_PORTAL)

    signAllPublications()

    //...
}

[tapchicoma]

I think better to ask this in public Gradle Slack

[Tóth István Zoltán]

Looks like I have a solution (in case someone hits the same):

add auto-expand-secmem 0x300000 to .gnupg/gpg-agent.conf
killall gpg-agent