Build and sign APKs in Manifesto

Rebuild

In a project, tap Build and sign in the toolbar. Manifesto:

1. Compiles only the DEX files you changed.
2. Re-encodes changed resources.
3. Aligns and signs the output with Manifesto's debug key (V1, V2 and V3).

The result is a new APK next to the original, ready to install. To use your own key, run Sign on the result.

Sign

From an APK's Options → Sign:

• Pick schemes V1, V2, V3 and V4, signed with Android's own apksig. V4 needs V2 or V3.
• Choose Debug key for quick tests, or My keystore to use a .jks or .p12 keystore you imported in Signing Key.
• Keystore passwords are used for the signing operation only and are never stored.

The debug key ships inside the app and is public. Never use it for anything you distribute.

Anticonfuse

Anticonfuse deobfuscates a copy of the APK. It gives obfuscated classes, methods and fields readable names and simplifies confusing branches in the DEX code, then rebuilds and (optionally) signs the result. The original file is left untouched. Only deobfuscate apps you own or are allowed to analyze.

Clone

Clone saves a snapshot copy of the APK in Manifesto's clones folder, so you can experiment freely.

For every option explained step by step, see how to sign an APK on Android.