Some checks failed
Android CI Build / check (push) Has been cancelled
Android CI Build / package-apks (push) Has been cancelled
Docs Deploy / build (push) Has been cancelled
Module Market Check / Validate modules/ (push) Has been cancelled
Module Market Publish / Generate submissions.json (push) Has been cancelled
Docs Deploy / deploy (push) Has been cancelled
- Package rename com.webtoapp -> br.com.drukstech.codeapp - Product rename WebToApp/web-to-app -> DruksCode/drukscode - Design system Wta* -> Dkc* - applicationId br.com.drukstech.codeapp (.play for gplay flavor) - rootProject.name DruksCode - Fresh git history (upstream kept as remote for sync)
28 lines
1.2 KiB
Markdown
28 lines
1.2 KiB
Markdown
# Google Play
|
|
|
|
Export a generated app as a Play-ready signed AAB. Open it from [⋮ → Google Play](/guide/main-screen/more).
|
|
|
|
## AAB export
|
|
|
|
One tap runs the full pipeline, with visible stages:
|
|
|
|
1. **Building APK** — assemble the APK on demand.
|
|
2. **Assembling** — convert to AAB.
|
|
3. **Signing** — sign the bundle.
|
|
4. **Signed** — done; ready to share or upload.
|
|
|
|
- **targetSdk rewrite** — the AAB's `targetSdk` is rewritten to the Play-required level (currently 36).
|
|
- **Metadata** — protobuf metadata is generated locally.
|
|
- **Cancellable** — stop mid-build.
|
|
- **App count** — see how many apps are eligible.
|
|
|
|
## Keystore
|
|
|
|
Create, import, and manage the signing keys used for the AAB.
|
|
|
|
## Notes
|
|
|
|
- You can also launch AAB export for a specific app from its [Build APK](/guide/app-actions/build-apk) dialog.
|
|
- The generated APK keeps `targetSdk` 28 by default (required for fork+exec runtimes — Node.js, PHP, Python, Go, WordPress); only the AAB is rewritten for Play. WebView-only app types can optionally raise the standalone APK's `targetSdk` from the APK export section; see [Build APK](/guide/app-actions/build-apk).
|
|
- A pre-upload advisory and warning are shown before exporting.
|