Download android alpha track

This site is intended for U. Animal Healthcare Professionals. The product information provided in this site is intended only for residents of the United States. The products discussed herein may not have marketing authorization or may have different product labeling in different countries.

The animal health information contained herein is provided for educational purposes only and is not intended to replace discussions with an animal healthcare professional. All decisions regarding the care of a veterinary patient must be made with an animal healthcare professional, considering the unique characteristics of the patient. All trademarks are the property of Zoetis Services LLC or a related company or a licensor unless otherwise noted.

All rights reserved. Home Resources Press Pet Connections videos. Simple-mode users should not put more than one APK to any track. This section describes a typical way the Tracks API would be used. In this case, we assume you want to upload new versions of the APK for each track, and assign a number of users to receive a staged rollout version.

In practice, a developer would be unlikely to take all of these actions in the same operation; instead, you might update the beta version one day, create a staged release on "production" another day, and so on. Call the Edits. In the request body, pass a Edits. At this point, the APKs are still not available to users. As with other edits, the changes do not go live until you commit them. Call the Edits: commit method to commit the changes. After you do this, users on each track will be given the updated version of the APK.

As with all edits, it can take several hours for the changes to take effect. When you have a new version of your APK that you want to gradually deploy, you may choose to release it as a "staged rollout" version. If you do this, Google Play automatically deploys it to the desired fraction of the app's users which you specify. If the "rollout" APK doesn't have any issues such as crashes, etc. This section describes the steps you would go through to perform a staged rollout of an APK, then promote it to production:.

Upload a new APK to the edit, using the Edits. Start a "inProgress" staged release on the production track using the Edits. Choose the fraction of users who should receive the new APK. At this point, the APK is still not available to any end users. Commit the changes in the active edit by calling Edits: commit.

Over the next few hours, the new APK will be rolled out to users. The fraction of users you select will receive the new APK. Depending on the success of the staged rollout you may then wish to increase the percentage of users eligible for that release or halt the release.

Change the "inProgress" staged release on the production track using the Edits. Set the status to "halted". Your release will no longer be available to new users. If you later decide to resume a halted release you can do so by setting its status back to "inProgress".

To create a draft release on a track:. When releasing a new version of your application you can highlight what's new to users by specifying release notes on your release.