Android App Bundle (.aab) Toolkit + GUI

Open Source Development
1

ZebDroid Bundle Studio

A desktop toolkit for analyzing, inspecting, modifying, validating, and testing Android App Bundles (.aab).

Built with Java (Swing) by Zuhaib.

03_overview_done
03_overview_done1280Ɨ820 9.83 KB

01_home
01_home1280Ɨ820 5.74 KB

Features

:package: AAB Analyzer

Analyze any .aab file and get a detailed breakdown of:

  • Manifest
  • Modules
  • Resources
  • Bundle structure

:label: App & Package Name Editor

Change the application Label (App Name) and Package Name directly inside an existing App Bundle.

:bullseye: Target SDK Editor

Change the Target SDK version of an existing bundle without rebuilding the application from source.

:writing_hand: AAB Signer

Sign an App Bundle using your own keystore.

:white_check_mark: AAB Validator

Perform structural and Play Store readiness checks before publishing.

:magnifying_glass_tilted_left: AAB Inspector

Deep-dive into the internal contents and structure of an Android App Bundle.

:microscope: AAB Compare

Compare two .aab files and identify differences between their contents.

:rocket: Play Preflight

Run pre-upload checks designed to help identify potential Google Play Console issues before submission.

:mobile_phone: Universal APK Builder

Generate a Universal APK from an App Bundle for quick sideload testing.

:desktop_computer: Guided Desktop GUI

A clean Java Swing interface where you select a bundle once and access relevant actions such as:

  • Edit
  • Inspect
  • Validate
  • Preflight
  • Compare
  • Build APK

No need to remember CLI menu numbers.

:gear: CLI-Powered GUI

The GUI is a frontend for the real CLI engine. Results displayed by the GUI come directly from the underlying CLI tools.

Technology

  • Java
  • Java Swing
  • Android App Bundle (.aab)
  • Bundletool
  • CLI-based processing

Author

Zuhaib

Built with :heart: by ZebDroid.

Download

Download the latest release of ZebDroid Bundle Studio from the GitHub Releases page.

Required Tools

Some bundled tools are distributed separately because of their file size.

:down_arrow: Download BundleStudio Tools Package

The package contains the required tools for AAB analysis, inspection, signing, APK generation, and other bundle operations.

1 Like
New aab files created by MIT app inventor not uploading to Google Play
2

How to use it?

4

Future Updates

More AAB analysis, editing, validation, comparison, Play Store checks, and developer tools are planned for future releases.

5

You can convert the APK to an AAB first, then use the tool to change the package name of the AAB. After that, convert the modified AAB back into APK.

Simple workflow

1. APK ā†’ AAB
First, convert your existing APK into an AAB using an APK-to-AAB conversion tool. My AAB Toolkit currently does not include APK ā†’ AAB conversion.

2. Change the package name
Open the generated AAB in my Android App Bundle (AAB) Toolkit GUI and change the package name.

https://community.appinventor.mit.edu/t/android-app-bundle-aab-toolkit-gui/175950

3. AAB ā†’ APK
After changing the package name, use bundletool to generate APKs from the modified AAB.

4. Sign the APK
Sign the generated APK with your signing key and test it on your device.

That's the basic workflow:
APK ā†’ AAB ā†’ Change Package Name ā†’ AAB ā†’ APK ā†’ Sign & Test

New aab files created by MIT app inventor not uploading to Google Play
6

Actually, you can make it even simpler:

  1. Build the app as an AAB directly from App Inventor.

  2. Open the AAB with my Android App Bundle (AAB) Toolkit GUI and make the required changes, such as changing the package name.

  3. Convert the modified AAB to APK using bundletool.

  4. Sign the APK and test it.

So the workflow is simply:

App Inventor ā†’ AAB ā†’ AAB Toolkit ā†’ Modified AAB ā†’ APK

You can find the toolkit here:
Zebdroid Bundle Studio

1 Like
7

Thanks but the tool is failing to run.

8

can you please share more detail about failure

9

image
image807Ɨ362 6.7 KB

10

install java

11

Thank you. (Obviously Iā€™m not tech-savvy.) Installed Java now but still getting the same error message.

12

Please install JDK 17 (LTS) first. Make sure you install the JDK, not just Java/JRE.

After installation:

  1. Close the current CMD/terminal completely.

  2. Open a new CMD.

  3. Run:



java -version
javac -version

You should see the Java and javac versions.

If java works but javac still says "not recognized", add your JDK bin folder to Windows PATH. For example:



C:\Program Files\Java\jdk-17\bin

Then open a new CMD and run:



javac -version

Once javac is recognized, run the Bundle Studio/AABForge launcher again.

13

https://www.oracle.com/java/technologies/javase/jdk17-0-13-later-archive-downloads.html