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

fastlane traces: check and release status warn, scan reports fastlane-upload when a Fastfile / Appfile or a CI file or script still runs fastlane supply, deliver or pilot (file:line, storebound import fastlane); test, pitfall 96

Browse source
This commit is contained in:
CRTkafa 2026-10-22 01:39:14 +08:00
parent e03cbbe8aa
commit 4f993a906a
7 changed files with 140 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

11
skills/store-pitfalls/SKILL.md
View file

@ -1166,3 +1166,14 @@ that fails without the fix (see CONTRIBUTING.md).
- **Do:** run the command again later; after a release, warm the CDN cache by fetching every installer once.
- **Guard:** `download` in `cli/desktop.ts` reads in chunks, prints progress every 10 % and fails after 60 s without
data (`tests/desktop-dist.test.ts`).
## 96. A project still uploaded with fastlane and storebound never said so
- **Symptom:** the Play listing or build changed behind storebound's back; CI ran `fastlane supply` (or `deliver` /
`pilot`) next to the storebound config, and `check`, `scan` and `release status` were all quiet.
- **Cause:** storebound looked only at its own config; fastlane files and CI upload calls were never read.
- **Do:** run `storebound import fastlane` (MCP `import_fastlane`) to bring the metadata over, then replace each
upload call with the storebound command and remove the lane. Keep a lane only on purpose (`scan.ignore`
`fastlane-upload` with the reason).
- **Guard:** `findFastlaneTraces` in `cli/lib/fastlane-traces.ts` (Fastfile / Appfile, CI files and scripts with
`fastlane supply|deliver|pilot`); `check` warns, `scan` reports `fastlane-upload` with file:line, `release status`
warns per app (`tests/fastlane-traces.test.ts`).