The new version doesn't show up in the Play Store
A release takes a while to reach testers, and the Play Store's cache can hide it. Wait a few hours, then clear the Play Store cache.
What you see
The developer announced a new version, but the Play Store still offers the old one, or shows no update.
Why
A new release takes time to reach testers, sometimes several hours. The Play Store app on the phone can also keep stale information in its cache. And if the developer rolls the release out gradually, only part of the testers get it at first.
What to do
For the tester:
- Wait a few hours, then open the app's page in the Play Store again.
- Clear the Play Store cache: touch and hold the Play Store, tap “App info”, then “Storage & cache” › “Clear cache”. Labels vary a little between phone makers.
- Open the app's page again from the tester app.
Don't clear the data of Google Play services: Google keeps that for a last resort.
For the developer: check that the new release is rolled out on the closed testing track and shows “Published”. If testers still get the old version, see the version code ("Testers still get the old version: the version code is too low").
What Peerbeta does
When the developer announces an update, testers get a notification, and the next day's mission is about what's new.
Was this helpful?
Your feedback shapes what we write next.
The app crashes at start for several testers
Next →Testers still get the old version: the version code is too low