I am trying to create an Android release build following https://bitbucket.org/blog/automate-publishing-your-android-application-with-bitbucket-pipelines-and-gradle and we are hitting a few problems.
I've created a upload key and cert on Google Console and a Google service account.
The output from the Build task (assembleRelease) does not sign the build. The reason I say this is two reasons, one the APK gets names "unsigned" but more so when I try to upload the APK to Release Management / App Release of Google Console I get an error stating "Error from apksigner: ERROR: JAR_SIG_NO_SIGNATURES: No JAR signatures", which is the same message if I try to upload a Debug build I've built using Studio. I can manually upload a Release APK built via Studio so I think my Upload key is value.
Any thought on what I may be missing? Or suggestions of what to look at ... or a working gradle script and pipeline yml would be greatly appreciated.
@David Brown Did you find any solution? I'm also facing the similar issue.
Wasn't able to do it using bitbucket's own ci image, that was still giving me an error but then I used some different image.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must sign your build with the keystore in order to create a release build
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.