Has anyone built an android mobile app and uploaded to the Google Play store using App Signing by Google Play?

HCL Volt MX Volt MX Forum
1
This thread was migrated from an old forum. It may contain information that are no longer valid. For further assistance, please post a new question or open a support ticket from the Customer Support portal.

I am getting a successful release build of my android mobile app, but cannot upload it to the google play store because of the error: "You uploaded an APK that is not signed with the upload certificate. You must use the same certificate."

Though I have set the keystore aliases and passwords in the visualizer project settings, it appears that the build continues to use the debug keystore...

Here is an excerpt from the console log:

...

[exec-shell] :validateSigningRelease

[exec-shell] :packageRelease

[exec-shell] :assembleRelease

[exec-shell]

[exec-shell] BUILD SUCCESSFUL in 1m 49s

[exec-shell] 27 actionable tasks: 27 executed

signApk:

[echo] Release apk signing started.

[copy] Copying 1 file to A:\\pndDriver\\build\\outputs\\apk\\debug

[echo] Invoking APKSigner.jar to sign apk

[java] Getting .andorid folder location

[java] Checking key folder Path = C:\\Users\\sally\\.android

[java] Debug key exists at C:\\Users\\sally\\.android\\debug.keystore

[java] Debug Key not expired

[java] Signing the Apk=A://pndDriver//build//outputs//apk//debug//pndDriver-debug.apk with debugkey=C:\\Users\\sally\\.android\\debug.keystore

[java] Running command =C:\\KonyVisualizerEnterprise8.1.0.0\\java\\jdk\\bin\\jarsigner -sigalg MD5withRSA -digestalg SHA1 -keystore C:\\Users\\sally\\.android\\debug.keystore -storepass android -keypass android A://pndDriver//build//outputs//apk//debug//pndDriver-debug.apk androiddebugkey

[java] jarsigner: unable to sign jar: java.util.zip.ZipException: invalid entry compressed size (expected 27003 but got 27863 bytes)

[java]

[java] Process Exit status = 1

[java] Could not sign the Apk=A://pndDriver//build//outputs//apk//debug//pndDriver-debug.apk\tusing debugkey=C:\\Users\\sally\\.android\\debug.keystore

...

I am wondering if anyone else has run into this situation... and how it was resolved.

Thank you!

2

@Joe Fishew​ , Use unsigned release mode apk and sign it manually. Probably this could resolve the issue.

Choose the binary available in the apk folder and the path is \build\luaandroid\dist\BBCertApp\build\outputs\apk (eg: D:\Workspace\temp\BBCertApp\build\luaandroid\dist\BBCertApp\build\outputs\apk).

Please refer to link below for signing the APK

https://developer.android.com/studio/publish/app-signing

3

@Joe Fishew​

Please indicate the Kony Viz version you are using.

If you have provided release keystore the APK signed with your key store should be available in below path which is generic Android release apk generation path.

pndDriver\\build\\outputs\\apk\\release\\pndDriver-release.apk

You should be able to upload pndDriver-release.apk to playstore.

Attach the complete build log, incase you see issues there .

You can ignore the debug keysigning logs, as we by default sign the apk with debug keystore present in .android folder under user's home, which enables user to test the apk immediately after building in release mode .

This is done as unsigned apk's can't be installed in device.

Thanks for bringing it to our notice , we shall skip debug signing incase release keystore is provided in our next hotfixes to avoid confusion.

4

Adding this new article to the thread for further assistance. Android Signing Configuration in Visualizer Starter . https://basecamp.kony.com/s/article-detail/a046A00000DkadFQAR/android-signing-configuration-in-visualizer-starter