On this page
The problem
A tester installs or updates to a different version than the one you just published to the test track — often the production build.
Why it happens
Play delivers releases by version code. Users eligible for more than one track receive the release with the highest version code — and production beats testing tracks. If production carries a higher version code than your test release, testers get the production build. Internal testers are also a special case: they're not eligible for open and closed testing tracks even when listed there.
The quick fix
Compare version codes across tracks in Play Console. For testers to receive a test build, their track's release must carry a higher version code than anything they're eligible for on other tracks.
Step by step
List the releases per track
Open each track (Internal, Closed, Open, Production) and note the version code of the latest release on it.
Check what the tester is eligible for
A tester opted into closed testing is eligible for closed and production. An internal tester is only eligible for internal.
Compare version codes
The highest version code among the eligible tracks wins. If production's code is higher, that's the build the tester receives — raise the test release's code, or stage the production release lower.
Reinstall from the opt-in page
After correcting codes and publishing, have the tester reinstall from the test's opt-in page rather than the store listing.
Things to check
- Version codes on every track the tester is eligible for
- Which tracks the tester actually opted into
- Pending or in-review releases that haven't gone live yet
If this didn't work
- Give a newer test release a few hours to propagate after publishing.
- Ask the tester to fully uninstall before reinstalling from the opt-in link.
Common mistakes
- Releasing to production with a higher version code than the test track
- Assuming testers are only served from the track you shared even if they're also on other tracks
- Forgetting that internal test opt-in blocks open and closed track builds
When to contact Google
If version codes and eligibility are correct and a tester still gets the wrong build, use Play Console support with the exact track and version details.
Sources & references
Official Google documentationThese links open Google's official Play Console Help pages used to verify this guide. AppsTestLab guidance is independent and not affiliated with Google.
Last reviewed August 17, 2026 · Google Play requirements change — verify in the Play Console.