"Version Code Already Used" and Other Upload Errors That Stall a Google Play Closed Test

Praveen — Tue, 20 Oct 2026 10:14:43 +0000

Nothing stalls a Google Play closed test quite like an upload that won't go through. Your testers are waiting on the opt-in page, the 14-day window can't start for them until there's a release to install, and Play Console is showing a red error under the bundle you just dragged in.

These are the upload errors I've run into most on the closed track, what each one actually means, and the fix that works.

1. "Version code 1 has already been used. Try another version code."

Every bundle you upload to an app needs a versionCode higher than any bundle uploaded before, on any track. That includes builds you uploaded to Internal testing and then threw away. Play Console remembers them.

Fix it in your module's build.gradle.kts:

android {
    defaultConfig {
        versionCode = 7      // bump this on every upload
        versionName = "1.0.6"
    }
}

versionName is what testers see and can repeat. versionCode can't. I check App bundle explorer in Play Console to see the highest code already used, then go one above it. If you build in CI, derive it from the build number so you never think about it again.

2. "Your Android App Bundle is signed with the wrong key"

The message includes the SHA-1 fingerprint Play expects. Compare it with your keystore:

keytool -list -v -keystore upload-keystore.jks -alias upload

If the fingerprints differ, you probably signed with the debug key or an old keystore from another project. Find the right upload keystore and rebuild. If the upload key is truly lost and your app uses Play App Signing, the owner can request an upload key reset from the App integrity section in Play Console. It takes a while to go through, so don't plan a tester start date around it.

3. "You uploaded a debuggable APK or Android App Bundle"

You built the debug variant, or something set debuggable true on release. Build the release variant (./gradlew bundleRelease) and check that no buildTypes block flips debuggable on. This one bites people who copy a release config from an old sample.

4. Target API level errors

Play sets a minimum targetSdk for new apps and updates, and it moves up over time. If your upload is blocked for its target API level, raise targetSdk to the level named in the error, then actually run the app on a recent Android version before you upload again. New target levels change behaviour (permissions, background work, edge-to-edge), and you'd rather find that yourself than have a closed tester find it on day three.

5. "You need to use a different package name"

Package names are permanent and unique across Play. If you used com.example.* or a name that's already taken, change applicationId and create the app again in Play Console. This is a good moment to pick the final name, because you can't rename it later.

After the upload works

A successful upload isn't the finish line. Before inviting anyone:

Roll the release out on the closed testing track, not just Internal testing. Internal testers don't count toward the 12-tester, 14-day requirement for newer personal accounts.
Open Publishing overview and send the changes for review if they're waiting there.
Make sure your testers list (email list or Google Group) is saved on the closed track and the opt-in link works from a tester's phone.

If testers are the next problem

Once the build is live, the requirement is at least 12 testers opted in continuously for 14 days. If you can't gather that many people, 12testers.pro is one budget option: a managed closed test for $8 per app, with 14 physical Android devices joining through a Google Group or your opt-in link and a 16-day monitored window. No Play Console password is shared, and Google still makes the final production access decision. Their Google Play closed testing checklist for production access is a handy pass to run before you apply.

Fix the upload, check the track, then get your testers in. In that order, the 14 days start counting as early as they can.

DEV Community: Praveen