Play Store Distribution
With Updraft you can directly upload a build to the Google Play Store.
This feature is available with the Resign-Plan & Enterprise Plan
Requirements
An Google Play Integration is configured
Be an Owner or Admin
You have already created an app within your Play Store Account once
.aab file is uploaded to the internal testing track within the integrated Play Store account
Upload to the Play Store with Updraft
Press on the green Distribute-dropdown on the top right and select App Store.
Now you can select the Google Play Integration, which you want to use to publish your build and then press on Next.
The next step is to select the App which you want to distribute.
Press on next and Updraft will check if your app exists on the Play Store Account. If Updraft found an App, you can proceed.
Select the track you want to distribute the app on (production/beta/alpha/internal). You can see the status of the tracks and the latest release version on that track
Now to the fifth page. Here you have an overview with informations about your upload. Select your build ( default is the newest ). If all info's are correct, you can proceed again.
The last step is to press on the Send Release-button. With that, Updraft will upload the build to the Google Play Store.
Internal testing track
Internal testing allows quick distribution of app builds to a small group of testers.
This test is used for initial QA checks. You can distribute your app to up to 100 invited testers. Feedback from these testers won’t affect your app’s public rating and is only visible to the Developer Account.
After publishing the internal test for the first time, it may take a few days for the test link to become available. After that, any new release will be available within a few hours. This build can be tested directly without a review.
For paid apps, testers can install the application for free.
Closed testing track (Alpha)
Closed testing allows distribution of pre-release builds to a controlled group of testers for broader QA before opening to the public. This test is used for deeper functional testing and early feedback collection. You can invite testers via email lists or Google Groups. Feedback from these testers won't affect your app's public rating and is only visible to the Developer Account. After publishing the closed test for the first time, the build goes through a Google Play review that can take a few hours up to seven days. Subsequent releases are typically available within a few hours. For paid apps, testers can install the application for free.
Open testing track (Beta)
Open testing allows distribution of pre-release builds to anyone who joins the test, providing real-world feedback before production release. This test is used for late-stage validation and gathering broad user feedback. Anyone can opt in via a public link or the Play Store listing. Feedback from these testers won't affect your app's public rating and is only visible to the Developer Account. After publishing the open test for the first time, the build goes through a Google Play review that can take a few hours up to seven days. Subsequent releases are typically available within a few hours. For paid apps, testers must purchase the application normally.
Production track
The production track is the public release available to all users on the Google Play Store. This is the final, stable build distributed to your target audience. It is visible to anyone browsing or searching the Play Store and contributes directly to your app's public rating and reviews. Each production release goes through a Google Play review that can take a few hours up to seven days, sometimes longer for first submissions or major updates. Staged rollouts can be used to release progressively to a percentage of users. For paid apps, the standard pricing applies.
Last updated