Skip to content
  • Features
    • Integration features​
    • Customization features
  • Pricing
  • Knowledge Base
  • Start building
  • Features
    • Integration Features
    • Customization features
  • Pricing
  • Knowledge Base
Start building

Getting started with Quikapp

1
  • How to create a app

Prerequisites

1
  • Prerequisites for Quikapp

Domain verification

1
  • How to Verify Your Domain

Integrations

6
  •  Google sign in:
  • Google AdMob
  • Google Analytics
  • Chatbot
  • Push Notification
  • What Is Integration?

Customization

6
  • What Is Customization?
  • App Icon
  • Splash Screen
  • Bottom Nav bar
  • Loading indicator
  • Pull to refresh

Permission

1
  • Permission

Build Configuration

2
  • Build configuration for iOS
  • Build configuration for Android

App Screenshot

3
  • What is App Screenshot?
  • What is App Screenshot (Android) ?
  • What is App Screenshot (ios) ?

How to

9
  • How to install Java
  • How to create keystore for Android
  • How to get Team ID
  • Configure  Push Notification for Android
  • Configure  Push Notification with APNs – iOS
  • How to Install openSSL
  • How to Create Provisioning Profile – iOS
  • How to create Certificate for iOS
  • App Store Connect API

Pricing

1
  • Pricing

Tickets

1
  • Ticket

FAQ

3
  • Build
  • Publish
  • Push Notification

Account Center Guide

1
  • Account Center
View Categories
  • Home
  • Docs
  • How to create keystore for Android

How to create keystore for Android

A keystore file (.jks) is essential for signing your Android applications before publishing them to app stores such as Google Play.

Prerequisites

  • Java Development Kit (JDK) installed
    Ensure the JDK is installed on your system. The keytool utility, required to generate the keystore, comes bundled with the JDK.

You can verify installation by running:

Copy to clipboard
1
keytool -version
  1. Step 1: Open Terminal or Command Prompt
    • Windows: Open Command Prompt or PowerShell
    • macOS / Linux: Open Terminal

Navigate to the directory where you want to store your keystore file. It’s recommended to keep it in a secure location (for example, a keystores folder).

Copy to clipboard
1
cd path/to/your/keystores

Step 2: Generate the Keystore File
Run the following command, replacing the placeholder values with your own details:

Copy to clipboard
1
keytool -genkeypair -alias your_key_alias -keyalg RSA -keysize 2048 -validity 10000 -keystore your_keystore_name.jks

Parameter Explanation

  • -alias – A unique name for the key (you will reference this during signing)
  • -keyalg – Encryption algorithm (RSA is recommended)
  • -keysize – Key size (2048 is standard for Google Play)
  • -validity – Number of days the key is valid (10000 ≈ 27 years)
  • -keystore – Name of the keystore file to be created

Step 3: Respond to Keytool Prompts
The keytool utility will ask you to enter the following information:

Keystore Password

  • Enter a strong password for your keystore
  • Re-enter the password to confirm (characters may not be visible)

Certificate Information

  1. What is your first and last name?
    first_name last_name
  2. What is the name of your organizational unit?
    Your department or team name
  3. What is the name of your organization?
    Your company name
  4. What is the name of your City or Locality?
    Your city
  5. What is the name of your State or Province?
    Your state or province
  6. What is the two-letter country code for this unit?
    Examples: IN, US, GB
  7. Is the information correct?
    Type yes and press Enter to confirm

Step 4: Verify Keystore Creation (Optional)
After the command completes, the .jks file will be created in the selected directory.
To verify its contents, run:

Copy to clipboard
1
keytool -list -v -keystore your_keystore_name.jks

You will be prompted to enter your keystore password to view the details.

Important Notes*

Security

  • Your keystore file is critical for app updates
  • Never share it publicly
  • Losing the keystore means you cannot update your app on the Play Store

Backup

  • Back up the .jks file securely
  • Store both the keystore password and key alias password in a secure, redundant location

Validity

  • The 10000 validity value sets the key for ~27 years
  • This is recommended because the same signing key must be used for all future updates

Google Play App Signing

  • Google Play can securely manage your app signing key
  • You upload apps using an upload key, reducing risk
  • Upload keys can be regenerated if compromised

Your Android keystore is now ready for signing apps and publishing to Google Play.

Updated on December 22, 2025

What are your Feelings

    Build powerful, fully customizable Android and iOS apps effortlessly with our platform no coding required. Empower your vision with professional features and seamless publishing.

    Facebook-f Instagram Twitter Youtube

    Get help anytime check out our

    Knowledge Base
    • Privacy Policy
    • Terms of Service
    • Refund & Cancellation Policy
    © 2026 Quikapp All Rights Reserved.