Why Is the Google Play Closed-Test Version Not Updating?

You may publish a new AAB to a closed test and still find that testers do not see an Update button in Google Play.

The Play Store cache is not always the cause. Start in Play Console by confirming which versionCode was published to which track.

Cause 1: The versionCode was not increased

Google Play primarily uses versionCode, not versionName, to identify a newer build.

android {
    defaultConfig {
        versionCode = 43
        versionName = "1.4.0"
    }
}

Changing only versionName from 1.3.0 to 1.4.0 does not create a new uploadable update if the versionCode remains the same.

Cause 2: The release was published to a different track

A build intended for internal testing may have been published to a closed track, or the reverse.

Confirm:

• App
• Track name
• Release name
• versionCode
• Publication date and time
• Tester list

When CI or automated publishing is used, include the target track in the build or deployment logs.

Cause 3: The release is still a draft or being processed

Uploading and saving an AAB does not necessarily make it available.

Possible states include:

• Waiting for review
• Publishing in progress
• Changes not yet submitted
• Release error
• Tester not included in a staged rollout

Open the target release in Play Console and confirm its current state.

Cause 4: The tester already received a higher versionCode from another track

When the same Google account participates in multiple tracks, Google Play may select the highest compatible versionCode available to that account and device.

Internal test: versionCode 50
Closed test: versionCode 48

If the closed test is then updated to versionCode 49, the device does not downgrade from 50 to 49. The closed-test update will therefore not appear as expected.

Cause 5: The new release is no longer compatible with the device

Changes in a new AAB can remove some devices from eligibility.

Check whether the new release changed:

• minSdk
• Required hardware features
• ABI support
• Screen requirements
• Countries or regions
• Manifest entries introduced by an SDK or library

Use App Bundle Explorer and the device catalog to compare the supported devices for the old and new releases.

Cause 6: The Google account changed

If the account used for opt-in differs from the account selected in Google Play, the tester may see a different track or no eligible update.

Ask the tester to report:

Google account used to opt in:
Account selected in Google Play:
Currently installed app version:

Cause 7: A debug build or differently signed APK is installed

An app signed with a different certificate cannot be updated by the Play-distributed version even when the package name is the same.

If a debug build installed from Android Studio remains on the device, first confirm whether its data can be removed safely. Then uninstall it and install the Google Play version again.

Cause 8: Google Play has not refreshed yet

Even after Play Console shows the release as published, there may be a delay before the update is shown on a tester’s device.

Tester-side checks:

1. Open the app’s Google Play page directly
2. Confirm the selected Google account
3. Restart the Play Store
4. Restart the device
5. Wait and check again later

Treat clearing the Play Store cache as a later troubleshooting step. Confirm versionCode and publication status first.

Make the installed version easy to identify

Display versionName in the app or make it easy to find through the device settings.

A developer-facing screen can also show versionCode.

val packageInfo = packageManager.getPackageInfo(packageName, 0)
val versionName = packageInfo.versionName
val versionCode = packageInfo.longVersionCode

Track updates in a release table

Troubleshooting sequence

1. Inspect the AAB’s versionCode
2. Confirm the target track
3. Confirm the release publication state
4. Check for a higher versionCode in another track
5. Check device compatibility
6. Confirm the tester’s Google account
7. Check the signature of the installed app
8. Wait and reopen the Google Play page

Summary

When an update does not appear, start with these three items:

A new versionCode
The correct release track
Completed publication processing

For a deeper explanation of version management, see Version Code Already Used: Why the Upload Fails and How to Fix It.