How to generate a Keystore for Android distribution on Google Play – Audiorista Help Center

To publish your Android app, you’ll need a keystore file, a secure file that identifies you as the app’s developer. This keystore is used to sign your app before it’s uploaded to Google Play.

In this guide, we’ll walk you through how to generate your own keystore file, step by step. Once created, you’ll be able to upload it to the Audiorista Dashboard, allowing us to build and distribute your app securely.

You need the Java Runtime installed on your computer

Before generating a keystore, make sure the Java Runtime is installed on your computer.

On macOS: Use Spotlight Search (press Command + Space) and type “Terminal” to open it.
On Windows: Open Windows Terminal or Command Prompt (search for cmd) by searching for it in the Start menu.

You can check by running the following command in your terminal:

java -version

If the command doesn’t work, you’ll need to install Java Runtime from: https://www.oracle.com/java/technologies/downloads/

An example of an error on Windows:

Generate the keystore via your terminal

Before running the command:

Create and securely store two strong passwords — one for the keystore password and one for the key password. You’ll be prompted to enter both during the command, so have them ready to copy and paste into the terminal. You can use any password generator of your choice.

Open your terminal and navigate to the folder where you want the keystore file to be saved.

You can use the following commands to move between folders:

cd [folder name]      # move into a folder
cd ..                 # move up one level

Once you’re in the desired location, run the command below (customized with your own details):

macOS:

keytool -genkeypair -v -keystore yourKeyStoreFileName.keystore -keyalg RSA -keysize 2048 -validity 10000 -alias yourKeyAlias

Windows command prompt:

"C:\Program Files\Java\jdk-25\bin\keytool.exe" -genkeypair -v -keystore yourKeyStoreFileName.keystore -keyalg RSA -keysize 2048 -validity 10000 -alias yourKeyAlias

Windows PowerShell:

& "C:\Program Files\Java\jdk-25\bin\keytool.exe" -genkeypair -v -keystore yourKeyStoreFileName.keystore -keyalg RSA -keysize 2048 -validity 10000 -alias yourKeyAlias

Replace:

yourKeyStoreFileName.keystore → with your chosen file name (keep the .keystore extension)
yourKeyAlias → with any word you’d like to use as the alias (for example: cherryblossom)
(Windows only) "C:\Program Files\Java\jdk-25\bin\keytool.exe" →
If you’re on Windows, the keytool command is typically located at:

"C:\Program Files\Java\jdk-25\bin\keytool.exe"

This path assumes you have Java 25 installed in the default location.

If you’re using a different Java version (for example, Java 17), simply replace jdk-25 with your version number — e.g.:

"C:\Program Files\Java\jdk-17\bin\keytool.exe"

If you installed Java in a different folder, update the path accordingly.

Running the command

Entering passwords

When you run the command, you’ll be prompted to enter your keystore password twice.
Note that when typing or pasting your password into the terminal, no characters will appear — this is a normal security feature on all systems.

If you’re only prompted once (for an initial entry and a repeat confirmation), it means your keystore password and key password are the same!

Entering Keystore Metadata and File Location

After setting your passwords, the terminal will prompt you to enter metadata about yourself as the keystore creator. You’ll be asked to provide details such as your name, organization, and city or locality.
Once completed, the keystore file will be saved in the folder you were in when running the command.

Add the keystore file and details to the wizard

Once your keystore file has been generated, go back to the Audiorista App Store Wizard.

Upload your newly created .keystore file.
Enter the following details in the corresponding fields:

Keystore password – the password you created for the keystore file
Key alias – the alias you chose (e.g., cherryblossom)
Key password – the password you created for the key itself (as mentioned above, might in your case be the same as "Keystore password")

Make sure each value matches exactly what you used when generating the keystore.