Android Question Custom Debug Keystore

Discussion in 'Android Questions' started by Chianca, Aug 16, 2019.

  1. Chianca

    Chianca Member Licensed 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?
     
  2. Brandsum

    Brandsum Active Member Licensed User

    Do you have the password of the provided jks file?
     
    Chianca likes this.
  3. Chianca

    Chianca Member Licensed User

    Yes! In release mode, I'm signin the APK manually, and it install sucessfully. But in debug mode, it fails.
     
  4. Brandsum

    Brandsum Active 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
     
    Chianca likes this.
  5. Chianca

    Chianca Member Licensed User

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

    Attached Files:

  6. Brandsum

    Brandsum Active Member Licensed User

    do you know the alias name of the keystore?
     
    Chianca likes this.
  7. Chianca

    Chianca Member Licensed User

    Yes, I have.
     
  8. Brandsum

    Brandsum Active Member Licensed User

  9. Chianca

    Chianca Member Licensed User


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

    upload_2019-8-16_17-42-57.png
     
  10. Brandsum

    Brandsum Active Member Licensed User

Loading...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice