Introducing Agents.·Read
OverviewAgentsWorkflowsExecutionDeveloper ToolsSecurityLibrary

Utilities

Read the base manifest from an AAB

Turn a supplied AAB base manifest into a readable native XML file.

Agent
Read package and SDK declarationsSeparate manifest extraction from bundle validationHandle AAB input instead of APK XML

overview

What bundletool-dump-manifest does

Supply an Android App Bundle FILE. The adapter invokes bundletool 1.18.3 dump manifest with the module fixed to base, then saves the native XML output. The manifest inside an AAB is protobuf data; this job reads it through bundletool rather than treating it as an APK binary-XML file.

Read package, version and SDK declarations from the emitted manifest. Extracting this XML does not validate the complete bundle, generate APKs, verify signatures or establish installability. Feature-module selection, XPath queries, signing and device connections are not exposed.

The AAB must be a nonempty local file of at most 20 MiB, with at most 5,000 ZIP entries, at most 20 MiB declared size per entry and at most 64 MiB declared total expansion. It must contain base/manifest/AndroidManifest.xml. The Java subprocess has a 90-second timeout and a 256 MiB maximum heap. Output and logs are checked against 4 MiB after execution; these checks do not bound peak memory or disk use.

source hub.docker.com/r/nenadzaric/skills-android-bundletool-dump-manifest

use cases

Where bundletool-dump-manifest fits

Read package and SDK declarations

Save the base manifest as XML for inspection or a later file-processing node. The owned fixture emits package org.trickest.fixture, version code 1, minimum SDK 21 and target SDK 28.

Separate manifest extraction from bundle validation

Use this job when you need the native XML artifact. Use bundletool-validate separately when the task is bundle validation; a successful manifest dump is not that result.

Handle AAB input instead of APK XML

Feed a supplied .aab file into the fixed base-module dump. Use androguard-manifest for APK Android binary XML rather than substituting an APK for this input.

reference

bundletool-dump-manifest inputs and flags

1 inputs
NameTypeFlagDescription
aabFILE--aabLocal Android App Bundle with its base-module protobuf manifest, within the file and declared ZIP limits.

Showing key inputs. bundletool-dump-manifest exposes 1 inputs in total.

example

Run bundletool-dump-manifest

bundletool-dump-manifest · command
bundletool-dump-manifest --aab owned-base.aab -o manifest.xml
sample output
  <uses-sdk android:minSdkVersion="21" android:targetSdkVersion="28"/>
  <application/>

guidance

Choosing bundletool-dump-manifest

Choose this node to extract readable base-module manifest XML from an AAB. Choose bundletool-validate for bundle validation or androguard-manifest for APK manifest decoding; the input format and output job differ.

bundletool-validate

Validate an Android App Bundle instead of extracting its base manifest XML.

androguard-manifest

Decode an APK Android binary-XML manifest rather than an AAB protobuf manifest.

faq

bundletool-dump-manifest questions

No. The fixed operation extracts the base manifest as XML. It does not run the separate bundle validation operation or establish that the bundle can be installed.

This adapter requires an AAB with base/manifest/AndroidManifest.xml and fixes the module to base. It has no feature-module selector. APK binary-XML decoding belongs to a separate job.

No. It exposes only an AAB file input and native XML output. APK generation, signing keys, device specifications and installation are outside the adapter contract.

The AAB must be a nonempty local file of at most 20 MiB, with at most 5,000 ZIP entries, at most 20 MiB declared size per entry and at most 64 MiB declared total expansion. It must contain base/manifest/AndroidManifest.xml. The Java subprocess has a 90-second timeout and a 256 MiB maximum heap. Output and logs are checked against 4 MiB after execution; these checks do not bound peak memory or disk use. Unsafe or duplicate member paths, symlinks and encrypted entries are rejected. A nonzero native exit becomes adapter exit 2; XML output must have a manifest root. Existing nonempty output is preserved.

The adapter uses bundletool 1.18.3 at upstream commit 586a43a450712a1067f3d92cf7574dee68226302. The accepted JAR and Java runtime layers are inherited unchanged from the existing bundletool image; the dump adapter has its own native tests. Native XML is saved without replacing it with a derived JSON summary.

The final local image passed nine native cases, including worker-style filenames, empty output, missing base manifest, bad protobuf and output preservation. Its three-node platform workflow passed with downloaded AAB, native XML and verifier checks for the package, version and SDK declarations. Public image and source/notices downloads have been verified anonymously. The original tool ID is public in the Library.

The source link provides immutable ORAS retrieval directions and a bundle SHA-256 for the actual adapter/build files, pinned bundletool source, original installed and embedded notices, and matching Java runtime source. The upstream core uses Apache-2.0 with original component terms retained. No exhaustive shaded-dependency composition or reproducible-build claim is made.

related

More Utilities tools

  1. browser-fetch

    Headless Chromium render: requested URL, final URL, status, and title next to the page.

  2. cewl

    Spider a URL and return a wordlist for password crackers.

  3. csvkit

    SQL on one CSV. The table name is the file stem.

  4. dnsgen

    Wordlist and mined-word subdomain permutation.

  5. duckdb

    In-process SQL on CSV, JSON, and Parquet. No server.

  6. edge-tts

    Microsoft Edge neural speech from text or a script file. No API key.

Run bundletool-dump-manifest yourself

Verbatim excerpt from native XML downloaded from the owned base-manifest platform run. The full output includes the manifest root and Android namespace declaration; this excerpt is not a complete XML document. SDK values are fixture declarations, not a device-compatibility result.

Open bundletool-dump-manifest in the libraryBuild a workflow with it

Facts on this page come from the live Trickest tool library.