A fast 2D and 3D game engine — TypeScript SDK, C++/WebAssembly core, visual editor. Ship one project to web, desktop, WeChat MiniGames, playable ads, and native Android / iOS.
TypeScript 2d-game-engine3d3d-game-engineandroidcppecsgame-editorgame-enginegamedeviostypescriptwebassemblywebglwebgpuwechat-minigame
docs: publishing to Google Play is a checkbox
esenginea641130bafa3
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex c595ec94f..fecf55e99 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -16,6 +16,15 @@ published separately; it ships inside the editor.### Added+- **Google Play: Package Project writes the App Bundle (`.aab`) too.** Play has+ required a bundle rather than an APK for new apps since 2021, so packaging for+ Android stopped at sideloading. Tick **Google Play App Bundle** in the Android+ section (or `cli native --package --aab`) and the export writes one beside the+ installable APK — the same content from the same template, with the manifest in+ aapt2's protobuf encoding and a JAR signature, which is what a bundle is. Still+ no JDK: the PKCS#7 block is written directly. The manifest is parsed once and+ written twice, so the bundle and the APK cannot describe different apps — a test+ decodes both and compares them, and CI validates the bundle with `bundletool`.- **Runtime templates are published with the release, and the editor downloadsthem.** The Android and iOS rows offer **Download** (with progress) beside*Install from file…* for offline installs and mirrors. What is downloaded isdiff --git a/docs/astro/src/content/docs/guides/mobile.mdx b/docs/astro/src/content/docs/guides/mobile.mdxindex c5ebbb3e8..45f58f3fb 100644--- a/docs/astro/src/content/docs/guides/mobile.mdx+++ b/docs/astro/src/content/docs/guides/mobile.mdx@@ -101,6 +101,11 @@ folder holds the finished app:(the same standing as Android Studio's debug key: fine for a device, refused byevery store). To sign with your own, pass `--key`/`--cert` to`node build-tools/cli.js native --package --content dist-android`.++ For **Google Play**, tick *Google Play App Bundle (.aab)* in the Android section:+ the export writes one beside the APK. Play has required a bundle rather than an+ APK for new apps since 2021 — it is the upload format, and cannot be installed on+ a device, which is why the APK is still what you test with.- **iOS** — an Xcode project: the `.xcframework`, the app shell and a generated`.pbxproj`, written around your content. Open it, pick your signing team under*Signing & Capabilities*, and Run.diff --git a/docs/astro/src/content/docs/zh-cn/guides/mobile.mdx b/docs/astro/src/content/docs/zh-cn/guides/mobile.mdxindex 374dad692..f98fcfa06 100644--- a/docs/astro/src/content/docs/zh-cn/guides/mobile.mdx+++ b/docs/astro/src/content/docs/zh-cn/guides/mobile.mdx@@ -85,6 +85,10 @@ Android 和 iOS 是**两个目标而不是一个"Mobile"**,因为它们被组装首次使用时生成的开发密钥签名(与 Android Studio 的 debug key 同等地位:装设备够用,任何应用商店都不收)。要用你自己的密钥,给`node build-tools/cli.js native --package --content dist-android` 传 `--key`/`--cert`。++ 要发 **Google Play**,在 Android 分区勾上 *Google Play App Bundle(.aab)*:导出会在+ APK 旁边再写一份。Play 自 2021 年起对新应用强制要求 bundle 而非 APK——它是上传格式,+ 无法直接装到设备上,所以你测试用的仍然是那个 APK。- **iOS** —— 一个 Xcode 工程:`.xcframework`、应用外壳和生成好的 `.pbxproj` 都已围绕你的内容写出。打开它,在 *Signing & Capabilities* 下选好签名 Team,Run。diff --git a/native/README.md b/native/README.mdindex dca080aa5..8169da02c 100644--- a/native/README.md+++ b/native/README.md@@ -209,6 +209,11 @@ all three formats are written directly (`build-tools/utils/{androidBinaryXml,zip* **Native libraries are stored, 16 KiB-aligned**, with `extractNativeLibs=false`:the OS maps them out of the package, which halves the install and is the postureAndroid 15's page size wants.+* **The App Bundle** (`--aab`, or the checkbox in the dialog) is the same content+ again: the manifest re-encoded as aapt2 protobuf (`androidProtoXml.js` — the same+ parsed tree and the same resource ids as the binary XML, so the two cannot+ disagree), laid out under `base/`, and signed as a JAR (`jarSign.js`). Play takes+ it; nothing else does, since a bundle is not installable.* **Signing is APK Signature Scheme v2** (minSdk 26 is well past the API 24 thatintroduced it, so v1's PKCS#7 would be dead weight), with an RSA key and aself-signed certificate in PEM under `<data>/android-keys`, generated on first