Jarsigner returned error #1 (it's not a problem with the keystore)

:information_source: Attention Topic was automatically imported from the old Question2Answer platform.
:bust_in_silhouette: Asked By unfa

I’ve been searching everywhere for a solution to why every export I’m trying to do ends with a jarsigner error.

I’ve generated my keystore over and over many times, changed all export settings in Godot both in the Project Export dialog and in the Editor Preferences dialog.

Nothing worked. I always got the same jarsigner error in the end.

:bust_in_silhouette: Reply From: unfa

I’ve found out why. I had JDK (Java Development Kit) version 7 installed, but I should only use 6 or 8 (really 8, because 6 is super old).

On Manjaro (or any other Arch-based Linux distribution) what I had to do was to install the jdk8-openjdk package and then check out what files it installed.

I was mislead by the fact it didn’t put anything into /usr/bin - so I was unable to locate the jarsigner binary at first. But it’s there. It’s full path was /usr/lib/jvm/java-8-openjdk/bin/jarsigner

I’ve put that into Godot’s Editor Preferences and it finally was able to sign my APK.

Another note regarding One-Click Deploy - you don’t have to install Android Studio.
You just need adb.

What I had to do was install the adb package and then run adb devices command.
This triggered my phone and it asked me for permission to allow my PC to connect via adb.

Only once I have confirmed that did Godot show the One-Click Deploy button, because it had access to my mobile device.

:bust_in_silhouette: Reply From: boy_hax

i had same problem and it resolved for me when i deleted the entries in the export menu
the debug section the keystore ,user name and password .
just make it empty there and fill it only in the editor,editor settings ,export, android

i hope this solve the problem for some one

:bust_in_silhouette: Reply From: pferft

In my case, as it turned out, in Android Studio it was crucial to delete all versions other than those listet in the docs:

Having some installed in parallel caused the troubles.