Open mindaugasnakrosis opened 3 years ago
+1 having the same issue here.
@ArshanKhanifar posted a stackoverflow question here: https://stackoverflow.com/questions/67604963/unable-to-sign-jar-invalid-entry-compressed-size
I realized my problem was that I was actually building a bundle
instead of an APK
. So I changed my releaseDirectory
to: releaseDirectory: android/app/build/outputs/apk/release
and also invoked ./gradlew
with assembleRelease
.
This fixed it for me. Here is my job file:
- name: Build Android App Bundle
run: |
cd android && ./gradlew assembleRelease --no-daemon
- name: Sign App Bundle
id: sign_app
uses: r0adkll/sign-android-release@v1
with:
releaseDirectory: android/app/build/outputs/apk/release
signingKeyBase64: ${{ secrets.ANDROID_SIGNING_KEY }}
alias: ${{ secrets.ANDROID_SIGNING_ALIAS }}
keyStorePassword: ${{ secrets.ANDROID_SIGNING_STORE_PASSWORD }}
keyPassword: ${{ secrets.ANDROID_SIGNING_KEY_PASSWORD }}
@mindaugasnakrosis Sorry I don't know about app bundles just yet so don't have anything to add to ur stackoverflow question for now.
I remember when I was making the key, there were two different ways to sign the app:
Make sure you did this by selecting the Android App Bundle option, not the APK option.
You can access this by: Build > Build Bundle(s) / APK(s)
I ran in to this issue, the fix was to remove the signingConfig signingConfigs.debug
line from within buildTypes
-> release
in build.gradle
I ran in to this issue, the fix was to remove the
signingConfig signingConfigs.debug
line from withinbuildTypes
->release
in build.gradle
Yeah, this fix helped me as well! Thanks!
I ran in to this issue, the fix was to remove the
signingConfig signingConfigs.debug
line from withinbuildTypes
->release
in build.gradle
Yes worked like Gem
I get an error in my github actions:
Preparing to sign key @ android/app/build/outputs/bundle/release with signing key /usr/bin/jarsigner -keystore android/app/build/outputs/bundle/release/signingKey.jks -storepass -keypass android/app/build/outputs/bundle/release/app-release.aab ***
jarsigner: unable to sign jar: java.util.zip.ZipException: invalid entry compressed size (expected 54105 but got 55476 bytes)
I found this answer:
https://stackoverflow.com/questions/5089042/jarsigner-unable-to-sign-jar-java-util-zip-zipexception-invalid-entry-compres
But it does not make any sense to me. How can it be already signed?
I found related issue: #31
however, it does not say how to solve the issue (at least I did not understand the solution)
My configuration file:
@r0adkll might you give me some leads how to debug this issue?