r0adkll / sign-android-release

A GitHub action to sign an APK or AAB
MIT License
360 stars 135 forks source link

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

Open ljunquera opened 2 years ago

ljunquera commented 2 years ago

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 commented 2 years ago

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

ayushkhare commented 2 years ago

I am getting the same error

banool commented 2 years ago

Still haven't found a fix unfortunately.

jemshit commented 2 years ago

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

banool commented 2 years ago

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.