Skip to content

How to Upload Your First App Bundle to Play Console

A walkthrough of your first upload: create the app, accept Play App Signing, choose a track, upload the .aab, fix errors and warnings, and send it for review.

Updated 3 min readBy the TestersZone team

Short answer

Create the app in Play Console, finish the store listing and App content, open a closed testing track, create a release, accept Play App Signing, upload your signed .aab, add release notes, review errors and warnings, then save and send for review from Publishing overview.

1. Create the app

Play Console → Create app. Enter the app name, default language, app or game, free or paid (free can’t later become paid), and accept the declarations. The package name is set by your first uploaded bundle.

2. Finish setup tasks

The dashboard lists setup tasks: privacy policy, app access, ads, content rating, target audience, data safety, government apps, financial features, health and others that apply, plus the main store listing. Closed testing requires completed app setup. See does a closed test need a store listing.

3. Create a closed release

  1. Go to Test and release → Testing → Closed testing and pick (or create) a track.
  2. Create new release.
  3. Play App Signing: for a new app, Google manages the app signing key by default. Keep the default unless you have a specific reason. See lost upload key.
  4. Upload your .aab. Play reads the package name, versionCode and permissions.
  5. Add release notes (see release notes for test builds).
  6. Next, then review errors and warnings.

4. Common upload errors

ErrorFix
Version code already usedIncrease versionCode. See this fix
Target API too lowTarget API 36 (since Aug 31, 2026). See target API 36
Signed with debug keyBuild a release variant signed with your upload key
Package name com.exampleChange applicationId before first upload
APK instead of AABNew apps must use App Bundles. See AAB vs APK

5. Testers, countries, publish

  • Testers tab: attach an email list or Google Group. See email list.
  • Countries / regions: add the countries your testers are in.
  • Open Publishing overview and send changes for review.

Then wait. First reviews can take longer (see stuck in review). Once published, copy the opt-in link and invite testers.

Frequently asked questions

Can I change free to paid later?

No. Once an app is published as free, it can’t become paid. You can add in-app purchases instead.

Do I have to use Play App Signing?

New apps use it by default, and it protects you if you lose your upload key. Keep the default unless you have a specific reason.

How large can my bundle be?

Google’s docs say the compressed download needed to install must be no more than 4 GB. Asset packs have their own limits.

Sources and how we keep this accurate

Policy facts are checked against Google's own documentation on the date shown above. Google can change requirements at any time, so confirm in your Play Console. Where we give advice or estimates rather than Google's rules, we say so. TestersZone is independent and not affiliated with Google. Drafts are AI-assisted and reviewed by our team.

Need 12 testers? Get them free.

Test 3 apps, earn 60 credits, and list your app for up to 20 real testers with verified daily check-ins.

Start free

Keep reading

How to Add Closed Testers With an Email List

Closed Test Release Stuck “In Review”: What to Do

How to Set Up a Google Play Closed Test (Step by Step)

How to Promote a Closed Test Release to Production

How to Choose Countries for Your Testing Tracks

How to Write Release Notes for Closed Test Builds

Browse all guides, or see the quick answers, guides and comparisons.