APPSINITYAndroid App Bundle
An App Bundle is a publishing artefact, not an installable one. On Appsinity it is converted with bundletool build-apks --mode universal, so anything that relies on split delivery does not survive.
Building a correct AAB
- Bundle, don't assemble. Gradle's
bundleRelease; in Unity, Build Settings → Build App Bundle. - Verify locally. Run
bundletool build-apks --mode universalyourself and install the output on a device. That is exactly what Appsinity produces. - Do not rely on Play Feature Delivery. Install-time restrictions, on-demand modules and distribution-targeting conditions are Play features. Universal mode ships them all to everyone.
- Keep the signing config separate. Appsinity signs the result with its own key; a signed-then-uploaded AAB is still re-signed here.
- Bump the version code. See APK versus AAB for why the manifest code is the only one that exists.
# what Appsinity runs on your bundle
bundletool build-apks --bundle=mygame.aab --output=mygame.apks --mode=universal
unzip -j mygame.apks universal.apk
zipalign -f 4 universal.apk universal.aligned.apk
apksigner sign --ks appsinity.keystore --ks-key-alias appsinity universal.aligned.apkSize consequences
Universal means every ABI, every density and every language ships to every player. Judge the download figure your listing will advertise by the universal APK, not by the AAB file you uploaded or by what Play reports.
Practical responses: cut unneeded ABIs at build time, replace density-specific art with one good asset, and drop language bundles you do not actually support in the UI.
What the format buys you here
So: upload an AAB because it is the same file you give Play, not because it improves delivery to Appsinity players.
| AAB capability | On Appsinity |
|---|---|
| Instant / on-demand feature delivery | No |
| Per-device ABI and density splits | No — universal |
| Device-targeting rules | Ignored; everything is included |
| One artefact across stores | Yes, the real benefit |
| Play App Signing key separation | Irrelevant — Appsinity uses its own key |
Frequently asked questions
Why does my download look bigger than the file I uploaded?
Because the artefact users receive is the universal APK built from it.
Can I upload both an APK and an AAB?
There is no multi-build selection UI. Whichever the listing's download chain resolves to is what users get, so upload one and point the listing at it.
Does the scanner reject anything in a bundle?
It scans the signed output. A bundle containing something suspicious after extraction fails the same way an APK would, see Malware policy.
Developer publishing support: [email protected]
General support: [email protected]
Partnerships: [email protected]