pub struct BuildBundle { /* private fields */ }
Expand description
§Build your app bundle using bundletool
To build your app bundle, you use the bundletool build-bundle command, as shown below:
bundletool build-bundle --modules=base.zip --output=mybundle.aab
§Note
If you plan to publish the app bundle, you need to sign it using jarsigner. You can not use apksigner to sign your app bundle.
Implementations§
Source§impl BuildBundle
impl BuildBundle
Sourcepub fn new(modules: &[PathBuf], output: &Path) -> Self
pub fn new(modules: &[PathBuf], output: &Path) -> Self
Specifies the list of module ZIP files bundletool should use to build your app bundle.
Specifies the path and filename for the output *.aab file.
Sourcepub fn config(&mut self, config: &Path) -> &mut Self
pub fn config(&mut self, config: &Path) -> &mut Self
Specifies the path to an optional configuration file you can use to customize the
build process. To learn more, see the section about customizing downstream APK generation
.
Sourcepub fn metadata_file(&mut self, metadata_file: &Path) -> &mut Self
pub fn metadata_file(&mut self, metadata_file: &Path) -> &mut Self
Instructs bundletool to package an optional metadata file inside your app bundle. You can use this file to include data, such as ProGuard mappings or the complete list of your app’s DEX files, that may be useful to other steps in your toolchain or an app store.
target-bundle-path specifies a path relative to the root of the app bundle where you would like the metadata file to be packaged, and local-file-path specifies the path to the local metadata file itself.