Delivering to Google Play

This page contains information about Google Play-specific delivery requirements and considerations.

For information on how to publish your application on Google Play, see Google Play.

Delivery requirements

Google Play has requirements an application must fulfil before you publish it. This section describes Google Play-specific requirements and explains how to meet them.

Android App Bundle

Google Play requires new apps to be an Android App Bundle (AAB) instead of an APK. For information on why, see The future of Android App Bundles is here.

To configure an application to be an AAB:

1. Select Edit > Project Settings.
2. In the Project settings window, select the Player tab, then open Android Player Settings:
   
3. In the Publishing Settings section, enable Split Application Binary.
4. Select File > Build Settings.
5. From the list of platforms in the Platform pane, select Android.
6. Enable Build App Bundle (Google Play). If you want to export the project and build it in Android Studio, enable Export Project then enable Export for App Bundle.

Now when you build the application, Unity builds the application as an AAB.

Application size

Google Play limits the install size of applications. The following table describes the size limitations Google Play has for each application type:

Application type	Size limitation
APK	If you split the application binary or use a custom expansion file, the APK must be smaller than 100MB and the expansion file must be smaller than 2GB. Otherwise, the APK must be smaller than 100MB.
AAB	If you split the application binary or use custom asset packs, the base module inside the AAB must be smaller than 150MB and the asset packs must fit the file sizes described in Android’s Download Size Limits documentation. Otherwise, the AAB must be smaller than 150MB.

For information on how to optimize the install size of your application, see Distribution size.

64-bit Architecture

Google Play requires applications to support 64-bit architecture. For more information, see Support 64-bit architectures. To make your application support 64-bit architecture:

1. Select Edit > Project Settings.
2. In the Project settings window, select the Player tab, then open Android Player Settings:
   
3. In the Other Settings section, enable ARM64. If your application targets Chrome OS, enable x86–64 (Chrome OS too. Note: You can only interact with this setting if your project uses the IL2CPP scripting backend.

Target API

Google Play requires applications to support a minimum target API. For information on what the current minimum target API is, see Meet Google Play’s target API level requirement.

To change your application’s target API:

1. Select Edit > Project Settings.
2. In the Project settings window, select the Player tab, then open Android Player Settings:
   
3. In the Publishing Settings section, set Target API Level to at least the target API level that Google Play requires.

App signature

Google Play requires applications to be signed. For information on how to sign your application, see Android Keystore Manager.

Considerations

This section contains Google Play-specific considerations to be aware of before you publish an application to Google Play.

Best practice checklist

To help launch an Android application successfully, Android’s documentation includes a best practice checklist of processes to follow. See Launch checklist.

Public symbols

If your application crashes on a device, Google can use a symbols package to make a native stacktrace human-readable on the Android Vitals dashboard. It is best practice to generate a public symbols package for your application and upload it to Google Play. For information on how to do this, see Generating a symbols package.