Skip to content
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

jarsigner error: java.lang.RuntimeException: keystore load: null #63

Open
ljunquera opened this issue Apr 19, 2022 · 5 comments
Open

jarsigner error: java.lang.RuntimeException: keystore load: null #63

ljunquera opened this issue Apr 19, 2022 · 5 comments

Comments

@ljunquera
Copy link

Here is the error I am getting:

Run r0adkll/sign-android-release@v1
Preparing to sign key @ /home/runner/work/myapp/mobile/build/outputs/bundle/release with signing key
Found 1 release files.
/opt/hostedtoolcache/Java_Zulu_jdk/8.0.322-6/x64/bin/jarsigner -keystore /home/runner/work/myapp/mobile/build/outputs/bundle/release/signingKey.jks -storepass *** -keypass *** /home/runner/work/myapp/mobile/build/outputs/bundle/release/mobile-release.aab ***
jarsigner error: java.lang.RuntimeException: keystore load: null
Error: The process '/opt/hostedtoolcache/Java_Zulu_jdk/8.0.322-6/x64/bin/jarsigner' failed with exit code 1

on my step:

- name: Sign Mobile Android release
  uses: r0adkll/sign-android-release@v1
  with:
    releaseDirectory: /home/runner/work/myapp/mobile/build/outputs/bundle/release
    signingKeyBase64: ${{ secrets.SIGNING_KEY }}
    alias: ${{ secrets.ALIAS }}
    keyStorePassword: ${{ secrets.KEY_STORE_PASSWORD }}
    keyPassword: ${{ secrets.KEY_PASSWORD }}
@banool
Copy link

banool commented May 13, 2022

I'm getting this error too, upgrading my Java version / build tools didn't help.

@ayushkhare
Copy link

I am getting the same error

@banool
Copy link

banool commented May 24, 2022

Still haven't found a fix unfortunately.

@jemshit
Copy link

jemshit commented Jun 9, 2022

You sure secrets are really valid, especially secrets.SIGNING_KEY?

@banool
Copy link

banool commented Jun 9, 2022

Pretty sure so. Nonetheless, I stopped using this in favor of just signing the output as part of the gradle build, which involves doing something like this: https://github.com/banool/aclip/blob/main/.github/workflows/full_ci.yml#L139-L140.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants