-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to load signer "signer #1" java.io.IOException: Invalid keystore format #1
Comments
You will need to base64 encode the entire file as the action decodes it straight to the disk. For example, I run this on my signing key: (I run this on macOS, so your implementation may differ) openssl base64 < some_key.jks | tr -d '\n' | tee some_key.jks.base64.txt Then I copy the contents of |
I could look into adding an optional input that just takes a raw key text and uses that to sign the key |
Perfect, that did the trick! Thank you so much! Really appreciate your work :) |
I am still facing this issue including converting base64 of jks. Verification succesful Any thoughts or guidance is super helpful. Have been stuck for two days on this issue. |
@me-at-syeds-me did you able to fix the issue |
Having this issue as well
Of interest, take a look at the exception :
|
i have the same issue:
|
@Kiperfy Seems that your error is here |
@r0adkll I use it in workflow(forked from https://github.com/577fkj/HMCL-PE) and I changed the key to mine, it dont work, but 577fkj says it works on his key(is my key's encrypt algorithm wrong?)
Also -list -v output:
Actions output:
|
I have the same issue.
|
Failed to load signer "signer #1" |
Hello, I'm trying to use this action to sign an apk, but I'm having an issue. I added the "ALIAS", "KEY_PASSWORD", "KEY_STORE_PASSWORD", and "SIGNING_KEY" to the Secrets tab in the project. The "SIGNING_KEY" is the shaded part between
-----BEGIN ENCRYPTED PRIVATE KEY-----
and
-----END ENCRYPTED PRIVATE KEY-----
I tried with BEGIN and END text, and got the same results.
Actual .yml file:
Log output showing the error:
The text was updated successfully, but these errors were encountered: