0.6.1

What's new

• build-apks --connected-device command now also builds instant apks.
• extract-apks now only extracts install-time modules for persistent (not instant) variants.
• get-device-spec command now also detects device features.
• New flag --overwrite in the device-spec command to overwrite the output file if it already exists.
• Added support for ANDROID_SERIAL environmental variable to specify a particular device as an alternative to device-id in get-device-spec, install-apks and build-apks commands. If both are present device-id's value is choosen.

0.6.0

What's new

• Native libraries are stored uncompressed and page aligned in the APK for devices on Android M and above. This lets applications use less space on the device as well as generate smaller updates on the Play Store.

0.5.1

What's new

• Added support for generation of instant APKs.
• Added support for multiple level of dependencies between features.

Also, adding tests to the repo.

0.5.0

What's new

• Added support for --device-spec flag in the build-apks command in order to build APKs only for a specific device.
• New flag --overwrite in the build-apks command to overwrite the output file if it already exists.
• Flags can now be passed in format --flag=value or --flag value.

Bugs fixed

• install-apks command now also able to install to pre-L devices.
• Embedded wear APKs now also signed when a keystore is provided.
• Fix split name of the fallback for language assets directory.

0.4.2

What's new

• Added optional --connected-device flag to the build-apks command. When specified, a cut-down APK Set archive will be created containing APKs optimized only for the connected device. This will reduce the build time, but the APK Set is guaranteed to support only that specific device.

• When using extract-apks, install-apks and build-apks with the --connected-device flag, we are now checking compatibility of the connected device or the device spec file with the App Bundle or APK Set. The error will be returned if the compatibility check fails (for example because of unsupported ABI).

Bugs fixed

• Added handling of a tilde sign (~) on Linux/Mac platforms across all path flags (#12)
• Fixed the "No connected devices found" issue during local deployment (#11)
• Better error handling of the get-device-spec command errors if the device spec cannot be fully fetched.

0.4.1

What's new

• Added optional --modules flag to extract-apks and install-apks commands. When specified and the device matches split APKs, then only APKs of the specified modules will be extracted.

Bugs fixed

• Fix NullPointerException thrown by extract-apks and install-apks commands on Windows.

0.4.0

What's new

• Language splits enabled by default for all bundles. If not desired, this can be disabled in the gradle config.

• For bundles built with bundletool 0.4.0, the dist: prefix is now enforced on all attributes of the <dist:module> tag in the AndroidManifest.xml (for on-demand modules).

• For bundles built with bundletool 0.4.0, resources with the default density are moved to config splits if they have alternative density configurations, and resources with a single density configuration are moved to the master split.

• Read the persist.sys.locale value of the device to detect the current language selected on the device when present.

• standalone is now a valid module name.

0.3.3

First public release

Commands available

• build-bundle: Builds an Android App Bundle from a set of precompiled modules.
• build-apks: Generates an APK Set archive containing all possible split APKs and standalone APKs.
• extract-apks: Extracts from an APK Set the APKs that should be installed on a given device.
• install-apks: Installs APKs extracted from an APK Set to a connected device.
• get-device-spec: Writes out a JSON file containing the device specifications of the connected Android device.
• validate: Verifies the given Android App Bundle is valid and prints out information about it.
• version: Prints the version of bundletool.

Documentation

Official documentation

Issues

Report any issue you find on our Issue Tracker.