(This places the APK in a storage area, but does not release Pass the APK in the method's requestīody. You might update the beta version one day, create a staged release onĮach APK you want to upload. Would be unlikely to take all of these actions in the same operation instead, We assume you want to upload new versions of the APK for each track, and assignĪ number of users to receive a staged rollout version. This section describes a typical way the Tracks API would be used. Advanced-mode users using the multiple APKĬan upload zero, one, or more APKs to each track. Simple-mode users should not put more than one APK to any YouĬan make use of staged releases on 'production' track to safelyĭeploy your release first to a small percentage of production usersĪnd then gradually increase this percentage as your confidence in Releases on the 'production' track are deployed to all users. Track as configured in the Google Play Console. Internal versions of your app are deployed to your internal test

Users to these groups using the Google Play Console. You assign to the alpha and beta test groups. Testing tracks such as 'alpha' and 'beta'Īlpha and beta versions of the app are deployed to the users (If the edit isĭeleted or discarded, any APKs uploaded to that edit are also This method uploads the APK into a storage 'bucket', where it canīe assigned to a 'track' to deploy it to users. The app, until you finally deploy that version as the 'production' You can gradually increase the number of users who get that version of Once you have released the staged rollout version, Version, which is automatically made available to a small number of This also allows you to deploy a staged rollout

This allows you toĭeploy alpha and beta versions of your app, which are made available The Google Play Developer API allows you to upload new APKs for your appsĪnd release them to different release tracks.

Latest apk play store