Struct crossbundle_tools::types::BuildBundle

pub struct BuildBundle { /* private fields */ }

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

impl BuildBundle

pub fn new(modules: &[PathBuf], output: &Path) -> BuildBundle

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

pub fn config(&mut self, config: &Path) -> &mut BuildBundle

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

pub fn metadata_file(&mut self, metadata_file: &Path) -> &mut BuildBundle

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

pub fn run(&self) -> Result<(), Error>

Runs bundletool commands to build AAB

Trait Implementations

impl Debug for BuildBundle

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.