question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot sign with in-memory key '[...]:signMavenPublication' because it has no configured signatory

See original GitHub issue

As explained in the README: https://github.com/vanniktech/gradle-maven-publish-plugin#signing I moved to in-memory GPG keys, using the following Gradle properties:

signingInMemoryKey=...
signingInMemoryKeyId=...
signingInMemoryPassword=...

I used gpg --export-secret-keys --armor $KEY_ID and assigned the data to signingInMemoryKey. I also tried with the base64 version. It really seems the key is well decrypted, because when I did it wrong I had the error Could not read PGP secret key, and I do not have it here.

I did not change my gradle code, but now it fails with the message: Cannot perform signing task '[...]:signMavenPublication' because it has no configured signatory You can see the gradle code here: https://github.com/aldebaran/pddl-planning-android/blob/a97d0656b7fe65cc0668b37c9e0da89e044932f0/pddl-planning/build.gradle

And the full error report with the stacktrace here: https://pastebin.com/3aiRjsZz

I am probably doing something wrong, but I cannot find any clue about it in the README.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:8 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
twyattcommented, Jun 6, 2021

I encountered this failure when I had one or more of my singingInMemory* properties configured incorrectly.

At first, my singingInMemoryKey wasn’t stripped of the header, footer and newlines (as described in https://github.com/vanniktech/gradle-maven-publish-plugin/pull/201#discussion_r584270633).

Then, I had specified the wrong signingInMemoryKeyId. I ultimately ended up just removing this property, as it is optional.

I also had specified the password under signingInMemoryPassword before realizing that I was missing the Key portion of the property name (i.e. it is supposed to be signingInMemoryKeyPasswordMavenPublishBaseExtension.kt#L121).

0reactions
gabrielittnercommented, Jun 20, 2021

As @twyatt mentioned the readme had the wrong property name. Sorry for the confusion

Read more comments on GitHub >

github_iconTop Results From Across the Web

Gradle build configured signatory - java - Stack Overflow
What went wrong: Execution failed for task ':signArchives'. Cannot perform signing task ':signArchives' because it has no configured signatory.
Read more >
The Signing Plugin - Gradle User Manual
The GnupgSignatory relies on the gpg2 program to sign the artifacts. Of course, this requires that GnuPG is installed. Without any further configuration...
Read more >
Cannot perform signing task 'signReleasePublication ...
... of the task i getting an error 'Cannot perform signing task ':mylibrary:signReleasePublication' because it has no configured signatory'
Read more >
Cannot perform signing task signMavenJavaPublication ...
直接编译的时候执行里面的task会提示编译不过,报错信息Cannot perform signing task ':signArchives' because it has no configured signatory.// .
Read more >
Building Gaelyk - Cause: Cannot perform signing task
Cause : Cannot perform signing task ':signArchives' because it has no configured signatory. Steven's profile photo ... I think tt will need a...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found