App Store / Google Play · 清单验收 · 不承诺过审Telegram @hagee66

上架通

GOEE LISTING LEDGER

№ ENgoee.cc
账号归你 · 邀请协作


2026-03-01

AAB upload and size: common Play bundle issues

AAB vs APK, common upload failures, and bundle size with feature modules. Shared terminology for engineering and listing. Telegram @hagee66.

This guide · Guide library · Apple listing · Google listing · Both stores · Telegram @hagee66

Google Play distribution for new apps and updates centers on Android App Bundle (AAB). Teams often clash when engineering is used to APK sideloads while ops cannot find the upload entry in Console—or when AAB upload fails and “package too big” is assumed when the real issue is signing or versionCode. This note explains AAB vs APK, upload failure triage order, and size/module caveats in one language for engineering and listing, and ties to Play release tracks and materials. Play rules on format, size caps, and device-generated APKs change—follow official docs. Upload success does not guarantee review approval. For Goee collaboration at goee.cc, contact Telegram @hagee66.

What this guide solves

  • Why Console wants AAB while local testing still uses APK.
  • Upload errors—versionCode must increase, invalid signature, missing Play App Signing confirmation—mistaken for network issues and re-uploaded endlessly.
  • Bundle bloat: uncompressed assets, duplicate ABIs, debug symbols, unsplit resources hurting download experience and reviews.
  • Dynamic Feature / Asset Delivery enabled but store copy does not say “some content downloads later,” conflicting with user expectations.
  • iOS build-number thinking mixed with Android; versionCode not incremented so upload is blocked.

Who should read

Role Use
Android engineer Release bundle, signing and versionCode
Listing operator Upload to the right track, read common English errors
Product Optional modules, honest “first download size” messaging
QA “Installed from Play” vs adb install APK behavior

Pre-upload materials and declarations: precheck scorecard; keys: signing handoff.

Core practice

AAB vs APK: where each is used

Dimension AAB APK
Submit to Play Standard flow New apps and updates usually require AAB (exceptions per official docs)
Local debug / CI smoke AAB rarely installed directly adb install works
What users download Play-optimized APK / splits per device Your universal APK is often larger
Size perception Bundle size ≠ user download size Single APK is what you see

Team convention: signed release AAB for Play; APK or internal track link for tester smoke tests.

Hard checks before upload

  1. versionCode strictly greater than the highest value on any Play track (including internal). Cross-check iOS versioning to avoid cross-platform release-day chaos.
  2. Signing with the correct upload key; verify Play App Signing in Console. See signing handoff.
  3. targetSdk / permission changes—sync Data Safety and store copy, not just the bundle.
  4. Track choice: internal / closed / etc., per Play release tracks.

Upload failure: triage in order

1. versionCode not incremented → bump code and rebuild
2. Signature / upload key mismatch → keystore / Play reset state
3. Package name ≠ Console app → check applicationId
4. Required metadata incomplete → Console prompts (rating, policies) first
5. Transfer / browser → new network, official upload method if offered
6. Banned components or policy conflict → match bundle to declarations, not purely technical

Paste full error text into the release log—do not screenshot only “Upload failed.”

Size: engineering levers

  • Assets: WebP/vectors over huge PNGs; density-specific assets, not universal giants.
  • ABI: bundle splits—avoid stuffing every .so into one APK mindset (per Gradle/AGP).
  • Locales: resConfigs for shipped languages, aligned with store localization.
  • Debug: release off debug flags, strip unused resources (test R8/Proguard rules).
  • SDKs: ads, analytics, maps often hit size and permissions—sync SDK disclosure.

User complaints about “200MB download” may be first install plus asset modules; store copy can honestly note “some content downloads on first use” (must match real behavior).

Feature modules and Play Asset Delivery

If using dynamic features or large asset delivery:

  • Test tracks must validate whether first open / first level needs extra download.
  • Weak network and low storage need clear UI, not silent crash.
  • Console and listing must not promise “fully offline” if core assets are fetched online.

Details per current Google Play docs—this guide does not enumerate every module type.

Terms listing needs

Four numbers from engineering: versionName, versionCode, bundle file size, one-line delta vs last release. Template release notes to avoid “uploaded but which version?”

Copy-paste templates

AAB upload log

[AAB upload log]
App:
Package name:
Target track: internal / closed / open / production
versionName:
versionCode (> any live value):
AAB SHA256 (optional):
Upload key owner:
Change vs previous:
New permissions / SDKs: Y / N; Data Safety rechecked: Y / N
Uploader:
Upload time:
Console result: processing / live on track / failed (full error)
Test install by:

Size review (major release)

[Size review]
Version:
Bundle size:
Vs previous: + / - MB
Main deltas:
New SDK:
User-facing extra-download note (store / in-app):
One improvement for next week:

Failure capture

[Upload failure]
Time:
versionCode:
Full English error:
Ruled out: network / browser / account permission
Next action:
Owner:

Common mistakes

  1. Debug-signed AAB uploaded. Release track needs release signing.
  2. versionName changed, code did not. Play keys off code, not your opinion of “new version.”
  3. APK size assumed to be user download size. Sample real install size from Play builds.
  4. Upload success → production without internal smoke. See release track guide.
  5. Locales stripped but store still targets that country. Broken UI after install.
  6. Console pre-launch hints ignored. Pair with pre-launch report.
  7. iOS and Android ship same day with one release note but mismatched version numbers. Separate code/build per platform.

FAQ

Must tests use AAB?
Internal tracks usually take AAB; local testing can use APK. Follow the current upload UI.

How fast after upload can I install?
Processing takes time; country and track vary. Log “processing complete” time—do not assume instant.

Over the size limit?
Caps and expansion delivery per official docs. Run a size review and module split first—do not try to evade checks.

Can APK and AAB coexist?
Policy is current-Google; new apps are AAB-first. Do not rely on outdated dual-upload blog posts.

Do failed uploads affect review counts?
Failed uploads usually do not consume a user-visible version; repeated bad packages may draw policy attention. Fix then re-upload.

Hermes / 16KB page size and new requirements?
Follow official notices and Console prompts—this guide is not a compliance bulletin.

Next steps

  1. Fill AAB upload log before the next release, merge with Play release tracks checklist.
  2. Signing handoff and versionCode rules.
  3. Google Play materials items for bundle and permissions.
  4. Major releases: size review plus SDK inventory.
  5. Dual-platform: iOS version and build numbers.

Related reading

Back to guide library · Google listing · Telegram @hagee66