'jarsigner' returned with error #1

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

I’m using 3.0 stable, today I tried exporting and I got that error. Since that never occurred to me, I searched for clues here, but, as mentioned in a couple of questions, re-generating the keystore didn’t work.
After a bit of struggling I found out the error was due to the fact that I had previously renamed some assets inside the editor, but I did not notice that Godot made a copy of the file with the new name, keeping another copy with the old name.
Basically I fixed the error by deleting the old copies: somehow having the same textures with different names breaks the exportation process. Is this normal or a bug? Should I raise an issue on GitHub?

you can see better logs when you run godot tool in terminal.
try to find what’s wrong with running in terminal.

volzhs | 2018-02-07 18:06

I restate that the cause of the error is having the same file with two different names; in this case two PNGs.
Anyway, this is the last piece of error in the terminal:

jar is unsigned.
Uninstalling previous version: Xiaomi MI 5
running cmdline: "E:/SDK/adb.exe" "-s" "ee3fe10d" "uninstall" "org.godotengine.dualwield"
Installing into device (please wait..): Xiaomi MI 5
running cmdline: "E:/SDK/adb.exe" "-s" "ee3fe10d" "install" "-r" "C:\Users\Davide\AppData\Local\Temp/Godot/tmpexport.apk"
2507 KB/s (26070171 bytes in 10.153s)
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION: Failed to parse /data/app/vmdl567776369.tmp/base.apk: AndroidManifest.xml]
running cmdline: "E:/SDK/adb.exe" "-s" "ee3fe10d" "shell" "am" "start" "-a" "android.intent.action.MAIN" "-n" "org.godotengine.dualwield/org.godotengine.godot.Godot"
Starting: Intent { act=android.intent.action.MAIN cmp=org.godotengine.dualwield/org.godotengine.godot.Godot }
Error type 3
Error: Activity class {org.godotengine.dualwield/org.godotengine.godot.Godot} does not exist.

DodoIta | 2018-02-11 09:41