Skip to main content

Upload AAB

In RuStore Console, you can download files in AAB format (Android App Bundle). This will reduce the size of the file that the user downloads from RuStore, while the installation will be much faster.

How to download an app in AAV format​

  1. Open the RuStore Console system.

  2. Click the "Applications" tab.

  3. Click "Add an app".

  4. Enter the app name in the pop-up window.

  5. Click "Add".

  6. Select the added app.

  7. Click "Upload a new version".

  8. Upload your app signature files in .aab format

  9. Download the AAV file.

img

AAB File Upload Requirements:​

Application signatures must be added separately before loading the .aab file.

  • The app file must weigh no more than 500 MB;

  • Use a unique package name;

  • the assembly must be tested and configured.

Loading an app signature​

For Android App Bundle you need to download the app signature:

  1. Go to the block with the warning “Signature not loaded” and click “Download”.

  2. In the new window, click "Download" and download the PEPK tool.

  3. Click the "Copy" button to copy the command with your unique encryption key

  4. Adjust the command by specifying your data instead of Russian values.

  5. Run the tool that exports and encrypts the private key using the adjusted command in a terminal. Replace the arguments and enter the vault and key passwords when prompted.

java -jar pepk.jar --keystore=your_key_store.keystore --alias=key_name --
  1. Download the ZIP archive created using the PEPK tool.

When migrating from .apk to .aab format, the signing certificate must match the signature fingerprint of the previous version.

How to check signature fingerprints?

Follow these steps to check whether the fingerprints of the RuStore public key signature certificate match your data:

  1. Export the verifiable public key signing certificate from your keystore to a PEM file:
    2. keytool -exportcert -alias sign_key_alias -keystore keystore_file -rfc -file cert.pem
  2. Get fingerprints for your PEM file and compare them with the fingerprints in RuStore.

Linux commands:

grep -v ^- cert.pem  | base64 -d | sha1sum
grep -v ^- cert.pem  | base64 -d | sha256sum
grep -v ^- cert.pem  | base64 -d | sha512sum
  1. Upload the upload key certificate that signed your AAB assembly in .PEM format.
img

Creating a signature for AAB​

To create a private key (sign key) for the Android App Bundle, which will subsequently be used to sign the .apk files of your app issued to users, follow these steps:

  1. Generate a new key pair (alias=sign) using the command in the terminal:
keytool -keystore .keystore -genkey -alias sign_v1 -keyalg RSA -validity 36500

sign —is the name of the key for signing the app.

  1. Copy the command for PEPK from the 2nd step of the signature download modal.

  2. Download the PEPK utility from the 1st step of the modal, then move this file to the system folder of the computer.

  3. Run the tool that exports and encrypts the private key using the adjusted command in a terminal. Replace the arguments and enter the vault and key passwords when prompted.

java -jar pepk.jar --keystore your_key_store.keystore --alias key_name --output new_path_for_created_certificate/pepk_out.zip --encryptionkey=your_unique_encryption_key  --include-cert

  1. Generate the upload key that signs your .aab file using the command:
keytool -keystore .keystore -genkey -alias upload -keyalg RSA
  1. Get the boot certificate from the previously generated boot key using the command below:
keytool -exportcert -alias upload -keystore .keystore -rfc -file uploadcert.pem

  1. Upload the ZIP archive created using the PEPK tool and the download certificate obtained from steps 4 and 6 into modal options 3 and 4 respectively.

  2. Go to the App Signature page and verify that the signature has been successfully uploaded and is displaying the appropriate information.