Uploading an App to Google Play: A Step-by-Step Guide for 2026

Introduction / Why This Is Needed

Publishing an application on Google Play is a key stage for reaching the audience of Android devices. This guide will walk you through all the steps in the Developer Console: from creating an app listing to launching a stable release. You will learn how to properly prepare builds, fill out required fields, and avoid common mistakes that lead to app rejection.

After completing this guide, your application will be available to millions of users through the official Google Play store.

Requirements / Preparation

Before you begin, ensure you have:

1. A Google Play Developer account (paid, $25 one-time fee).
2. A ready release build of your application:
   • Recommended format: Android App Bundle (.aab).
   • Alternative: Universal APK (.apk).
   • The build must be signed with your release key (not the debug key!).
   • versionCode in build.gradle must be higher than that of the previously uploaded version.
3. Listing assets:
   • App name (up to 50 characters).
   • Short and full description.
   • Screenshots (minimum 2 for phones, ideally for tablet and TV).
   • App icon (512x512 PNG, transparency is acceptable).
   • Promotional graphics (1024x500 PNG/JPEG).
   • Link to the privacy policy (mandatory if the app collects data).
4. Content information: category, age rating, developer address.

Step-by-Step Guide

Step 1: Create the App Listing in the Console

1. Open the Google Play Console and sign in.
2. On the main page, click "Create app".
3. Select the default language for the title and description.
4. Enter the app name. This is the name displayed in the store. It can be changed later, but with limitations.
5. Fill in the "Short description" (up to 80 characters) and "Full description" (up to 4000 characters). Clearly state the value and key features.
6. Click "Create app".

⚠️ Important: Once an app is created, it cannot be deleted. You can only "unpublish" it, but its history and statistics will be retained.

Step 2: Prepare and Upload the Release Build

1. In the left menu of the console, go to "Releases" → "Production" (or select another track: internal testing, alpha, beta).
2. Click "Create new release".
3. In the "Add from library" section, click "Browse" and select your .aab or .apk file.
4. The system will begin validating the build. This may take a few minutes. Ensure validation passes (green checkmark). Common errors:
   • "Invalid signature": You uploaded a build signed with the debug key. You need to build a release version.
   • "Low version code": Increase versionCode in app/build.gradle and rebuild the artifact.
   • "Target platform mismatch": Ensure minSdkVersion is not higher than that of 10% of active devices (usually API 21+ is sufficient).

Step 3: Fill in Release and Listing Information

After successfully uploading the build, fill in the required data:

1. "What's new in this version?" (release notes): Briefly list changes, fixes, and new features for existing users.
2. "Release name" (optional): An internal name for tracking, e.g., "v2.1.0 - Production".
3. "Countries/regions": Select the countries where the app will be available. All are selected by default.
4. "Pricing & availability":
   • Set "Free" or "Paid". A paid model cannot be changed to free after publishing.
   • Configure the publishing schedule (can be delayed to a future date).
5. "App content" (the most extensive section):
   • "App details": Category (Games, Apps), subcategory, tags (up to 5).
   • "Graphics": Upload the icon, screenshots (minimum 2 for phones), and promotional graphics. Adhere to resolution requirements.
   • "Description": Ensure the short and full descriptions are filled in for the selected language.
   • "Privacy policy": Provide the URL to your privacy policy. If the app does not collect data, check the corresponding box.
   • "Contact details": Support email, website (optional but recommended), phone number.
   • "Content rating": Complete the IARC questionnaire to determine the age rating.
   • "Target audience & content": Specify who the app is intended for (children, adults).

Step 4: Final Review and Rollout

1. On the right side of the screen, there is a "Publishing overview". All items must be green. If any are red, click on them to navigate to the incomplete field.
2. Ensure that in the "Releases" → "Production" section, the correct build is selected and all mandatory fields are filled.
3. At the top of the page, click the "Start rollout to production" button.
4. In the dialog box, confirm that your app complies with Google Play policies. Click "Rollout".
5. The release status will change to "In review". After successful review (from several hours to 3 days), the status will become "Published", and the app will appear on Google Play.

Verifying the Result

1. Via the console: The release status in the "Releases" → "Production" section should be "Published".
2. In the store: Find your app by name in Google Play. Open its page and verify that:
   • All screenshots and the icon are uploaded.
   • The correct description and age rating are displayed.
   • The "Install" button is active.
   • The "What's new" block appears in the description (if you added one).
3. For testing tracks: Ensure you have added tester email accounts to the tester list and received an invitation.

Potential Issues

Error "Failed to process your APK" or "Target platform mismatch"

• Cause: Your minSdkVersion is too high, or you are using outdated permissions.
• Solution: Check minSdkVersion in build.gradle. For maximum coverage, set minSdkVersion 21 (Android 5.0). Rebuild the artifact.

Error "Signature invalid" or "Debug certificate used"

• Cause: You uploaded a build signed with the debug.keystore key.
• Solution: Build a release artifact, specifying the path to your release.keystore and its credentials in build.gradle. Gradle command: ./gradlew bundleRelease or assembleRelease.

Rejection after policy review

• Cause: Violation of content policies (spam, malware, copyright infringement), incomplete filling of privacy fields.
• Solution: The console's "App policy status" section will indicate the exact reason. Make corrections (update description, remove prohibited content, add a privacy policy link) and create a new release.

App not appearing in Google Play search

• Cause: Indexing is in progress (can take up to 48 hours). Or the app is restricted by country/age.
• Solution: Wait 1-2 days. Check the "Countries/regions" and "Content rating" settings. Try searching for the app by its exact name.

Signing issues (App Signing by Google Play)

• Cause: If you enabled "App signing by Google Play" (recommended), Google stores the signing key. For updates, you must upload builds signed with the upload key you generated when first enabling this option.
• Solution: Do not lose your upload keystore (upload-keystore). If it is lost, it cannot be recovered—a new app (with a new package name) will be required. See the guide on recovering your Play App Signing key.