Download generated APKs using the Play Developer Publishing API
Stay organized with collectionsSave and categorize content based on your preferences.
You can download all APKs that Google Play generated from an app bundle
you've uploaded to Play Console using theGenerated APKsfeature in theGoogle Play Developer API.
How to use generated APKs
A typical publishing workflow which includes downloading generated APKs before
they are released on any track would be the following:
Create a new edit, by callingEdits: Insertand specifying the app you want to modify.
Assign the bundle to a track by callingEdits.tracks: update.
To avoid releasing the new version to end users at this stage, set the
status of the new release todraft.
Commit the edit.
Download the APKs generated from the bundle that you uploaded in step 2
using the Generated APKs methods in the API.
Process your downloaded APKs.
Create a new edit as you did in step 1.
Promote the draft release to a staged or full rollout by callingEdits.tracks: update.
Commit the edit.
How to construct your APK directory
If you need to use your APK files withbundletool, follow these steps to build
them using the Generated APKs API:
When calling the Generated APKs list method, the response will containTargetingInfofield for each signing key. Write this field value
to a file namedtoc.json.
Download your APKs, and put them in a directory with thetoc.jsoncreated
in the previous step. Note that each downloaded APK must be named
"DownloadId.apk", whereDownloadIdis the ID used to download the APK
from the Generated APKs download method.
You can now use this directory withbundletoolversion 1.15.2 or higher.
For example,bundletool install-apks --apks /path/to/created/directory.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-08-21 UTC."],[[["\u003cp\u003eDownload all APKs generated by Google Play from your app bundle using the Generated APKs feature in the Google Play Developer API.\u003c/p\u003e\n"],["\u003cp\u003eA typical workflow involves uploading a bundle, assigning it to a track as a draft, downloading generated APKs, processing them, and then promoting the draft to a staged or full rollout.\u003c/p\u003e\n"],["\u003cp\u003eTo use generated APKs with bundletool, create a directory containing a toc.json file with TargetingInfo from the API response and downloaded APKs named using their DownloadId.\u003c/p\u003e\n"]]],["Generated APKs, from app bundles uploaded to Google Play Console, can be downloaded via the Google Play Developer API. The process involves creating an edit, uploading a bundle, assigning it to a draft track, and committing the edit. Then, the APKs are downloaded. Optionally, a new edit is created to promote the draft release, followed by another commit. To use APKs with `bundletool`, a `toc.json` file is generated and combined with the downloaded APKs in a directory, each named \"DownloadId.apk\".\n"],null,["# Download generated APKs using the Play Developer Publishing API\n\nYou can download all APKs that Google Play generated from an app bundle\nyou've uploaded to Play Console using the *Generated APKs* feature in the\n[Google Play Developer API](/android-publisher).\n\nHow to use generated APKs\n-------------------------\n\nA typical publishing workflow which includes downloading generated APKs before\nthey are released on any track would be the following:\n\n1. Create a new edit, by calling [`Edits: Insert`](/android-publisher/api-ref/rest/v3/edits/insert) and specifying the app you want to modify.\n2. Upload a bundle by calling [`Edits.bundles: upload`](/android-publisher/api-ref/rest/v3/edits.bundles/upload).\n3. Assign the bundle to a track by calling [`Edits.tracks: update`](/android-publisher/api-ref/rest/v3/edits.tracks/update). To avoid releasing the new version to end users at this stage, set the status of the new release to **draft**.\n4. Commit the edit.\n5. Download the APKs generated from the bundle that you uploaded in step 2 using the Generated APKs methods in the API.\n6. Process your downloaded APKs.\n7. Create a new edit as you did in step 1.\n8. Promote the draft release to a staged or full rollout by calling [`Edits.tracks: update`](/android-publisher/api-ref/rest/v3/edits.tracks/update).\n9. Commit the edit.\n\n| **Tip:** Alternatively, if you want to avoid committing a draft release, you can release a new version of the app to an internal test track before downloading the generated APKs.\n\nHow to construct your APK directory\n-----------------------------------\n\nIf you need to use your APK files with `bundletool`, follow these steps to build\nthem using the Generated APKs API:\n\n1. When calling the Generated APKs list method, the response will contain **TargetingInfo** field for each signing key. Write this field value to a file named `toc.json`.\n2. Download your APKs, and put them in a directory with the `toc.json` created in the previous step. Note that each downloaded APK must be named \"**DownloadId.apk** \", where *DownloadId* is the ID used to download the APK from the Generated APKs download method.\n3. You can now use this directory with `bundletool` version 1.15.2 or higher. For example, `bundletool install-apks --apks /path/to/created/directory`."]]
