Skip to content

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.

docs(mobile): the instruction to give someone whose game crashed

yhhc697e45efa96
diff --git a/docs/astro/src/content/docs/guides/mobile.mdx b/docs/astro/src/content/docs/guides/mobile.mdx
index c27c77b71..0e059c7e6 100644
--- a/docs/astro/src/content/docs/guides/mobile.mdx
+++ b/docs/astro/src/content/docs/guides/mobile.mdx
@@ -298,13 +298,25 @@ adb pull /sdcard/Android/data/<your.package.id>/files/estella-boot.log
```
<Aside type="caution">
- `adb` is currently the only reliable way to get that file. Since Android 11 an
- app's `Android/data` directory is not readable by a file manager or by the
- system Files app — `adb shell` can only do it because that user is in the
- `ext_data_rw` group. So this works for you and for a tester who can plug in a
- cable; a player reporting a problem cannot fetch it themselves yet.
+ That path is for you, not for a player: since Android 11 an app's
+ `Android/data` is closed to file managers and to the system Files app, and
+ `adb shell` reaches it only because that user is in the `ext_data_rw` group.
</Aside>
+**When a game crashes, the next launch publishes the record where a player can
+get at it** — `Android/media/<your.package.id>/`, which a file manager lists,
+falling back to `Download/`. The file is named `estella-crash-<date>.log`, and
+the new run's own record says where it went:
+
+```
+previous run CRASHED; its record was copied to
+ /storage/emulated/0/Android/media/com.example.game/estella-crash-20260729-190738.log
+```
+
+So the instruction to give someone who reports a crash is: **open the game once
+more, then send the newest `estella-crash-*.log`** from that folder. Only crashes
+are published — a launch that finished leaves nothing there.
+
While a device is attached, the same lines are in `logcat`:
```bash
diff --git a/docs/astro/src/content/docs/zh-cn/guides/mobile.mdx b/docs/astro/src/content/docs/zh-cn/guides/mobile.mdx
index da44d89b7..4b1208bfe 100644
--- a/docs/astro/src/content/docs/zh-cn/guides/mobile.mdx
+++ b/docs/astro/src/content/docs/zh-cn/guides/mobile.mdx
@@ -256,12 +256,22 @@ adb pull /sdcard/Android/data/<你的包名>/files/estella-boot.log
```
<Aside type="caution">
- 目前 `adb` 是拿到这个文件唯一可靠的办法。Android 11 起,一个应用的 `Android/data`
- 目录不被文件管理器和系统「文件」应用读取——`adb shell` 能读只是因为那个用户恰好在
- `ext_data_rw` 组里。所以这条路适合你自己和能插数据线的测试同学;
- 报障的玩家目前还没法自己取。
+ 这条路径是给你的,不是给玩家的:Android 11 起,一个应用的 `Android/data` 对文件管理器
+ 和系统「文件」应用都是关的,`adb shell` 能读只是因为那个用户恰好在 `ext_data_rw` 组里。
</Aside>
+**游戏崩溃后,下一次启动会把记录发布到玩家能拿到的地方**——
+`Android/media/<你的包名>/`(文件管理器能列出),取不到时退回 `Download/`。
+文件名是 `estella-crash-<日期>.log`,新那次运行自己的记录里也会写明它去了哪儿:
+
+```
+previous run CRASHED; its record was copied to
+ /storage/emulated/0/Android/media/com.example.game/estella-crash-20260729-190738.log
+```
+
+所以给报障的人的说法是:**再打开一次游戏,然后把那个目录里最新的 `estella-crash-*.log` 发过来**。
+只有崩溃才会被发布——正常跑完的启动不会在那儿留下任何东西。
+
设备连着的时候,同样的内容也在 `logcat` 里:
```bash