CRT/storebound
1
0
Fork 0
Code Issues Pull requests Releases 1 Packages 1 Activity Actions

play build: find the Android SDK like Android Studio (ANDROID_HOME, ANDROID_SDK_ROOT, sdk.dir, default folder), pass it in the env, stop before Gradle when missing; doctor shows it. apple upload: size, per-part lines, 20 s heartbeat (api, altool, processing wait), per-part and per-call timeouts, --timeout exits 7 with the resume hint. Pitfall 25

Browse source
This commit is contained in:
CRTkafa 2026-10-12 08:48:02 +08:00
parent 3de295c294
commit 12eed58f41
15 changed files with 460 additions and 34 deletions
Download patch file Download diff file Expand all files Collapse all files

8
skills/build-and-sign/SKILL.md
View file

@ -64,6 +64,9 @@ when the owner said so for this run). The MCP server offers only `apple_signing_
(exit 0), INVALID / FAILED (exit 1, Apple emails the ITMS reason) or `--timeout` (default 60m, exit 7). Run long
uploads in the background with a log: `storebound apple upload --yes > .storebound/upload.log 2>&1 &` (only
after the owner's yes).
The upload is never silent: the size at the start, a line per part, a heartbeat every 20 s ("still uploading,
4m30s, 312/890 MB (35%), part 4/12"), the same while altool runs and while the build is processed. Past
`--timeout` it stops with exit 7; the same command again resumes the build upload (raise `--timeout`).
6. **Next.** `storebound apple encryption --build N`, `storebound apple testflight distribute --build N --group Team
--dry` (`testflight` skill), `storebound apple listing --version x.y.z --build N` (`appstore-first-release`).
@ -80,6 +83,11 @@ when the owner said so for this run). The MCP server offers only `apple_signing_
(or `--version-code N`) and where the key comes from. Then without `--dry`. The AAB lands in
`build/android/<package>-<versionCode>.aab`; storebound reads the versionCode back from the bundle and warns when
the build file ignored the one it passed (read `-PversionCode` there, or `android.injected.version.code`).
The Android SDK is found the way Android Studio finds it: `ANDROID_HOME`, `ANDROID_SDK_ROOT`, `sdk.dir` in the
Gradle project's `local.properties`, then `~/Library/Android/sdk` (macOS) / `~/Android/Sdk` (Linux) /
`%LOCALAPPDATA%\Android\Sdk` (Windows), and handed to Gradle through `ANDROID_HOME` / `ANDROID_SDK_ROOT`;
`local.properties` is never written. None found: it stops before Gradle and lists the places checked.
`storebound doctor` shows the SDK path and where it came from.
3. **Upload.** `storebound play upload --track internal --dry` (read-only: checks the versionCode is free, shows
what is on the track now and the release notes languages). Then without `--dry` after a yes. Tracks: internal,
alpha (closed), beta (open). Production stays `storebound play release --version-code N --production draft` plus