Publishing on Google Play
Google Play takes App Bundles (.aab), signed with your own upload key, that meet its yearly target API level and its rules for 16 KB memory pages. An App Bundle exported from Plasma meets the technical requirements. This page walks through a store build and explains how large games are split into asset packs.
What the Export Does for You
| Google Play requirement | How the export meets it |
|---|---|
| Target API level 36 | targetSdkVersion is 36. The preflight checks that platform android-36 is installed. |
| 16 KB memory pages | Native libraries are linked with NDK 28+ and aligned with the zipalign of build-tools 35+. |
| App Bundle format | Format: App Bundle builds the base module and asset packs with bundletool. |
| Upload key signing | Release keystore signs the bundle with your key. |
| Device features | The manifest declares Vulkan 1.3, so Google Play only offers the game to phones that can run it. |
| Download size limits | Data over the base module limit moves into install-time asset packs automatically. |
| Icons | Adaptive, monochrome (themed) and legacy launcher icons are built from the Icon settings. |
The minimum Android version is Android 10 (API 29).
Making a Store Build
- Create an upload key once. On the Android app tab, set Signing to Release keystore and click Create Keystore.... Save the
.jksfile outside the project and choose a password. The editor stores the password in Windows Credential Manager. Back up the file and password: every future update must be signed with the same key. - Set the identity. Check the Application ID. It cannot change after the first upload. Set the Version name.
- Set the format. Format: App Bundle · Google Play.
- Set the configuration. On the Build tab, set Configuration to Shipping. A Development bundle stays debuggable for testing on a device, and Google Play rejects it.
- Check the preflight. Fix every error. Read the warnings, especially Store listing images and the size checks.
- Export. Click Build App Bundle. The bundle is written to the destination folder as
<DisplayName>-<version>(<code>).aab. - Upload the
.aabin Play Console, together with the store icon and feature graphic.
With raise the code after each Shipping export on, the version code goes up by one after each successful Shipping export, so the next upload is accepted. The export log says version code raised to N for the next Shipping export.
To try a store bundle before uploading it, tick Install after build. The export becomes Build Bundle & Install and installs the bundle on the selected device with bundletool, including its asset packs.
Build machines
On a build machine without a credential store, give the export the signing secrets through environment variables:
| Variable | Contents |
|---|---|
PL_ANDROID_KEYSTORE_PASS | The keystore password. |
The keystore path and alias come from Editor/AndroidApp.ddl. Then run the export headless (see Exporting from the command line):
EditorProcessor -project <project> -exportProject Android -exportTarget D:/Exports/MyGame -exportConfiguration Shipping
Asset Packs
An App Bundle consists of a base module (the code, the manifest and the data that installs with it) and up to 100 asset packs. There are two ways data ends up in asset packs.
Automatic install-time packs
When the staged data is over Google Play's 500 MB limit for the base module, the build moves the data into install-time asset packs named gamedata…, each up to 1500 MB. They install with the app, and the game reads them as if they were part of the APK. The preflight shows Data in N install-time asset packs. You don't have to do anything.
Your own packs
Under Data delivery on the Android app tab, Add Asset Pack puts project folders into a named pack with one of three deliveries:
| Delivery | When the player gets it | Typical use |
|---|---|---|
| Install-time | With the app. | Content that must be there at first launch, kept separate for organisation. |
| Fast-follow | Right after the install. The game may already be running. | The levels after the first one. |
| On-demand | When the game asks for it. | Optional content, high-resolution packs, later chapters. |
The default for a new pack is On-demand. Fast-follow and on-demand packs use Google's Play Asset Delivery library, which the build adds when the project has such a pack. The game must handle a pack that is not there yet; see Asset packs at runtime.
In an APK, every pack installs with the app, so you can test all content without Google Play.
Size Limits
The preflight compares the estimated download with Google Play's limits. Sizes are compressed download sizes in MB (1,000,000 bytes).
| Limit | Value | Preflight warning |
|---|---|---|
| Base module | 500 MB | (handled automatically with install-time packs) |
| One asset pack | 1500 MB | Asset pack 'X' is over 1500 MB: split its folders over more packs. |
| Base module and all install-time packs | 4000 MB | Over the 4000 MB install-time download |
| All fast-follow and on-demand packs | 30000 MB | Over 30000 MB of fast-follow and on-demand packs |
| Everything the app downloads | 34000 MB | Over the 34000 MB Google Play allows an app |
| Asset packs per bundle | 100 | More than 100 asset packs |
These values come from Data/Tools/plEditor/Android/PlayRequirements.ddl in the engine. To test the automatic split with a small project, set PL_ANDROID_ASSET_PACK_LIMIT_MB to a lower pack size before starting the editor.
Store Checklist
- Release keystore set and backed up; no Signed with the debug key line in the preflight.
- Configuration: Shipping, Format: App Bundle.
- A clean device run on a representative phone: no missing shader permutations, no crash lines.
- Store icon and Feature graphic set (to check their sizes) and uploaded in Play Console.
- Version code higher than the last upload.