Releases: google/bundletool
Releases · google/bundletool
0.8.0
What's new
- Bundletool will no longer keep a list of extensions of files which must remain uncompressed by default in the generated APKs; it's up to the build system calling
build-bundle
to specify those files in the BundleConfig. Applies only to App Bundles built with version 0.8.0+ of bundletool. For users of the Android Gradle Plugin, this is a no-op since AGP already passes this list of files to bundletool. build-apks
command now signs the APKs by default with the debug keystore (when found) if--ks
flag is not passed. The debug keystore must be nameddebug.keystore
under the.android
subdirectory of one of the following locations:$ANDROID_SDK_HOME
, user home directory or$HOME
.- The
--modules
flag from theextract-apks
andinstall-apks
commands now supports the special value_ALL_
to extract/install all modules (without having to enumerate them all). - Resources can now be pinned in the master APK by specifying the resource IDs in the BundleConfig (see config.proto).
- The
split
attribute is no longer added automatically by Bundletool, it must be already present in the AndroidManifest.xml. Note that in the original AndroidManifest.xml, this attribute is namedfeatureSplit
(it is later renamed by aapt2). For users of the Android Gradle Plugin, this is a no-op since AGP adds it automatically.
Bugs fixes
dump manifest
command no longer fails when namespaces have been stripped from the manifest.- Fixed an issue where we did not remove activities and services from non instant modules in the instant base manifest.
dump resources
command now escapes the line breaks, quotes and backslashes from the strings of the values of resources.
0.7.2
What's new
- Flag
--universal
replaced with--mode=universal
(--universal
will be removed in a future release). - New support for generating standalone APKs to be put on the system image (
--mode=SYSTEM
) - New support for generating APEX files.
Bugs fixed
- 64-bit libraries no longer included in generated APKs if 32-bit RenderScript bitcode is present (not supported by Android platform).
0.7.1
0.7.0
0.6.2
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 thedevice-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
andbuild-apks
commands. If both are present device-id's value is choosen.
0.6.0
0.5.1
0.5.0
What's new
- Added support for
--device-spec
flag in thebuild-apks
command in order to build APKs only for a specific device. - New flag
--overwrite
in thebuild-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 thebuild-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
andbuild-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).