Closed meltanan closed 4 months ago
FYI, if I modify the signing script to: instead of SHA225withRSA TO SHA1withRSA and from SHA-225 To SHA1 signing is successful but I get an error when it tries to deploy that there is an issue with signature. And yes this is also for debug variant only!!! If I do it for release there is no issue.
Hi @meltanan, what task do you use from this repository? Could you share the full repro yaml and all repro steps? thanks
Hi @KonstantinTyukalov
Download secure file task
Generate bundle for debug task
Sign the generated bundle task
Copy files task
Publish build task
I shared the full yml file by two screen shots
@meltanan, as I see you do not use tasks from the Google Play extension. This repository is focused only on the Google Play extension tasks. In this case, please open a ticket in the tasks repo to have the right eyes on it. I'm closing this ticket, please let me know if you have any concerns.
Hey
I have my Azure pipeline building (release variant/environment), signing, and releasing app to production with no issues.
When I try to build the app for debug/beta variant/environment I get an error when it tries to sign the bundle. I'm using the same YML file, the only thing I changed in YML file ( from release to debug) is "tasks: ':app:bundleRelease'" ---> "tasks: ':app:bundleDebug'". and I was getting this error:
jarsigner: unable to sign jar: java.util.zip.ZipException: invalid entry compressed size (expected 7521 but got 7106 bytes).
I made sure there is no existing aab file and I did remove //signingConfig signingConfigs.debug
I'm not sure what I'm missing, or if I'm using the script correctly or building the bundle correctly using the task.
I attached screen shot of my YML file and the error page.
I appreciate any help please.