Android Question Custom Debug Keystore

Chianca

Member
Licensed User
Longtime User
Hello, I'm trying to debug my application into a Smart POS, based on Android 5.1, but it only accepts APK install with the .JKS key provided. When i connect to the B4a Bridge and run in debug mode, the App fails to install cause the Key used to sign, is the native debug keystore from B4A.

Is there any way to debug my application signing the APK with the provided .JKS file?
 

Chianca

Member
Licensed User
Longtime User
Yes! In release mode, I'm signin the APK manually, and it install sucessfully. But in debug mode, it fails.
 
Upvote 0

Brandsum

Well-Known Member
Licensed User
B4A > Tools > Private Sign Key > Select load existing key > Browse the JKS file and put the password in password field > then click on Ok
 
Upvote 0

Chianca

Member
Licensed User
Longtime User
B4A > Tools > Private Sign Key > Select load existing key > Browse the JKS file and put the password in password field > then click on Ok

I made this change, but when I'm running in Debug mode, it is failing with this attached message.
 

Attachments

  • image_2019_08_16T19_54_24_687Z.png
    image_2019_08_16T19_54_24_687Z.png
    25.6 KB · Views: 237
Upvote 0

Brandsum

Well-Known Member
Licensed User
Upvote 0

Chianca

Member
Licensed User
Longtime User
There are two ways either you change the alias / username of the keystore to b4a or you have to manually sign an apk with custom keystore file.

If you want to change the username of jks file then check this link to change the alias name https://blog.blundellapps.co.uk/tut-change-alias-passwords-of-your-android-keystore/

if you want to sign it manually then follow this process https://www.b4x.com/android/forum/threads/tutorial-how-to-sign-apk-with-non-b4a-keystore.14049/


Hi, I've changed the Alias name, and now, the error is:

upload_2019-8-16_17-42-57.png
 
Upvote 0
Top