Managing Your KeyStores

If you wish to override the buddybuild generated KeyStore during your build, you can upload your own. Buddybuild will pick up the uploaded KeyStore and use it for code signing your App.

Note

Release build keystores

Release builds — like the ones that eventually end up in the Play Store — will require to be code signed with a KeyStore that is associated with a Developer.

Caution

Verify the keystore

You can run keytool -list -keystore .keystore -alias foo to verify that the keystore alias and password matches

Step 1: Upload a Keystore from your development machine

Start by clicking on App Settings.

Builds   Settings.png

Next, select Build settings, then APK signing keystores.

Settings   APK Signing Keystores   menu.png

Locate the KeyStore on your local machine and upload it. It is typically a file with a .keystore or .jks extension. Enter your KeyStore password, alias and alias password.

Settings   APK Signing Keystores.png

Once uploaded, you will see your keystore listed on the page.

Settings   APK Signing Keystores   2.png

Step 2: Assign the keystore to an application variant

Next, assign your keystore to an application variant. Buddybuild will build and sign the variant with the selected keystore.

Settings   APK Signing Keystores   3.png

That’s it! Buddybuild will now use your uploaded KeyStore for subsequent builds.

results matching ""

    No results matching ""