Specifies filenames or patterns matching zero or more expansion files that should be associated with the APK files being uploaded to Google Play.

You can list as many or as few expansion files as you like — you have the option of associating previously-uploaded expansion files with the new APKs being uploading here.

Naming

Files must be named in the format [main|patch].<expansion-version>.<application-id>.obb

For example:

Patterns

You can use wildcards like "**/build/**/*.obb".
See the 'includes' attribute of Ant's FileSet for the exact format.
Note that multiple entries must be comma-separated.

The base directory is the build's workspace. You can only upload OBB files that are located in your workspace.

Re-using existing expansion files

If you don't provide a main or patch expansion file for every APK that you want to upload, enabling the "Re-use expansion files from existing APKs where necessary" option will automatically associate existing expansion file(s) with the APK(s) being uploaded.

With this option enabled, if not enough expansion files are provided for all of the APK(s) being uploaded, this plugin will search for the newest, previously-uploaded APKs on Google Play with main or patch expansion files, and will associate those files with the new APK(s) being uploaded here.

For example: If you want to upload a new APK, but the expansion files have not changed at all, you should leave the "Expansion files" field blank, but enable the checkbox.
At build time, the latest existing main (and patch, if available) expansion files will be associated with the newly-uploaded APK.

Similarly, if you have a new build, but only want to change the patch file, then just provide the patch expansion file and make sure this option is checked. The uploaded APK will have the existing main expansion file associated with it, along with the newly-uploaded patch file.

This field supports substituting environment variables in the form ${SOME_VARIABLE} or $SOME_VARIABLE at build time.