Increasing the user fraction for a staged rolloutĪssuming you have an ongoing staged rollout at 5%, as described in the previous The percentage of users eligible for that release or halt the release. Of users you select will receive the new APK.ĭepending on the success of the staged rollout you may then wish to increase Hours, the new APK will be rolled out to users. At this point, the APK isĬommit the changes in the active edit by calling Start a "inProgress" staged release on the production track using theįraction of users who should receive the new APK. Staged rollout of an APK, then promote it to production:Ĭreate an edit, as described in Edits Workflow. This section describes the steps you would go through to perform a Version when you are ready, you can deploy that APK as the new production If the "rollout" APK doesn't have any issues (such asĬrashes, etc.), you might increase the fraction of users who receive that Google Play automatically deploys it to the desired fraction of the app's When you have a new version of your APK that you want to gradually deploy, you mayĬhoose to release it as a "staged rollout" version. Take several hours for the changes to take effect.) After you do this, users on each track will be Other edits, the changes do not go live until you commit them.Ĭommit the changes. For example, to release anĪt this point, the APKs are still not available to users. In the request body,Ĭontaining the release you wish to rollout. To the APK when you release it on a track.įor each track that you want to release APKs on. It on a track or deploy it.) The method returns a version code forĮach APK you upload you will use this version code to refer (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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |