--export-keys fails with NPE in org.bouncycastle.openpgp.PGPSignature about gradle

[ljacomet]

The issue is in the backlog of the relevant team and is prioritized by them.

---

Thanks. We will take a look and confirm the regression aspect.

[ljacomet]

Hey @illarionov,

I cannot reproduce the issue locally. I tried Gradle 8.8 with JDK 17 and 21, and I always successfully export keys, wether I do it in one step (gradle -M pgp,sha256 --export-keys build -s) or two as you indicated.

Could you try again and see if there is something else specific to your environment that's causing the issue?

In the meantime, removing the a:regression label for now.

[illarionov]

It looks like a cached key was used on my machine, because after deleting the ~/.gradle/caches/keyrings, the error stopped reproducing.
I've prepared a repository with a slightly different way to reproduce this error: https://github.com/illarionov/playground-android-composite-build/tree/gradle-29395

Steps:

git clone https://github.com/illarionov/playground-android-composite-build.git -b gradle-29395
cd playground-android-composite-build/
./gradlew -M pgp,sha256 --export-keys -g /temp/temp_gradle build -s

Run on Github Actions: https://github.com/illarionov/playground-android-composite-build/actions/runs/9355109305/job/25749523071

Given that this issue can be resolved by deleting the ~/.gradle/caches/keyrings and gradle/verification-keyring.keys, I am uncertain whether a fix is necessary on Gradle. I leave this decision to the Gradle team.

[hegyibalint]

The issue is in the backlog of the relevant team, but the existence of a workaround means it might take a while before a fix is made.

---

Thanks for the clarification. The error should be improved to be more descriptive about potential workarounds for local cache cleanup.