Manage Google Play releases from Searvia
Upload store graphics, move a tested release from internal testing to production and control the staged rollout.
About 10 minutes
What You Need
- Google Play connected; the service account also needs the release permissions
- An app bundle (AAB) uploaded in Play Console or from your CI
- Owner or admin role in your Searvia account
- 1
Give the Release Permissions
Play Console › Users and permissions
In Play Console open Users and permissions, edit the service account and also allow “Release apps to testing tracks” and “Release to production, exclude devices, and use Play App Signing”.
- 2
Open the Release Tab
Project › Release
Open your Google Play project and choose Release. The checklist shows the listing, graphics, screenshots and tracks as Google has them now.
- 3
Add the Store Graphics
Release › Store Graphics
Choose a language and add the app icon (512 × 512 PNG), the feature graphic (1024 × 500) and at least two screenshots. Searvia checks Google’s size rules first; each upload is sent to Google for review.
- 4
Promote a Release
Release › Tracks and Releases
Under Tracks and releases click Promote on the track you tested, pick the target track, set the rollout percentage (below 100 starts a staged rollout), write the release notes per language and confirm.
- 5
Control the Rollout
For a staged rollout, raise the percentage, halt it if something goes wrong, resume it or release to everyone.
What You Get
Your release moves through the tracks from Searvia, with the summary of every change shown before it is sent.
- Data safety, content rating and target audience are answered in Play Console; Google’s API cannot change them.
- If changes are already in review, Google cancels that review and sends everything again together.