← back to Nineoh Guide
ASC-BATCH-BLOCKER-BOARD.md
47 lines
# iOS Submission Batch — Live ASC Blocker Board (read-only)
**Ticket:** TK-10363 (refresh) · orig TK-10355 · **Generated:** 2026-08-10 · **Source:** live App Store Connect API (account key `72Y2TZT54R`)
**Method:** ground truth generated fresh from `node ~/.claude/skills/ipa-status/scripts/ipa-status.mjs --ready`. For each app the *furthest-along* App Store version is used (ASC apps carry duplicate empty `1.0` draft records — see "Tooling note" below).
## Summary
| Bucket | Count | Apps |
|---|---|---|
| 🔵 In review (submitted — nothing to do) | 5 | Beverly Hills Videos, Celebrity Signatures, Charge & Explore, Homes on Spec, Unofficial 90210 Guide |
| ✅ Submit-ready (one Steve click in ASC) | 2 | Boomer Calc (1.0.1), GovArbitrage |
| 🔴 Intentionally dead (leave as-is) | 1 | 67 Calc (DEVELOPER_REJECTED — intentional 4.3-duplicate pull) |
| ⛔ Needs-prep (build + desc + shots) | 1 | Costa Rica |
**Only 3 apps need any action:** 2 are Steve-gated ASC-console clicks (Boomer, GovArbitrage), and 1 needs prep before it can be submitted (Costa Rica — a peer node is staging shots+desc now). 67 Calc is deliberately left dead and is NOT a submit candidate.
## Per-app board
| App | Bundle | ASC appId | State (best ver) | Ver | Desc | Shots | Verdict |
|---|---|---|---|---|---|---|---|
| Beverly Hills Videos | com.abrams.beverlyhillsvideos | — | WAITING_FOR_REVIEW | 1.0 | ✓ | 2 | 🔵 In review |
| Celebrity Signatures | com.abrams.celebsignatures | 6798448971 | WAITING_FOR_REVIEW | 1.0 | ✓ | 2 | 🔵 In review |
| Charge & Explore | com.abrams.chargeandexplore | 6797629330 | WAITING_FOR_REVIEW | 1.0 | ✓ | 2 | 🔵 In review |
| Homes on Spec | com.abrams.homesonspec | 6798873898 | WAITING_FOR_REVIEW | 1.0 | ✓ | 2 | 🔵 In review |
| Unofficial 90210 Guide | com.abrams.nineohguide | — | WAITING_FOR_REVIEW | 1.0 | ✓ | 2 | 🔵 In review |
| Boomer Calc | com.boomercalc67.app | — | PREPARE_FOR_SUBMISSION | 1.0.1 | ✓ | ✓ | ✅ Submit-ready |
| GovArbitrage | com.abrams.govarbitrage | — | PREPARE_FOR_SUBMISSION | 1.0 | ✓ | ✓ | ✅ Submit-ready |
| 67 Calc | com.sixtysevencalc.app | 6754257150 | DEVELOPER_REJECTED | 1.0 | ✓ | 2 | 🔴 Intentionally dead (4.3 pull) |
| Costa Rica | com.abrams.costarica | 6799240433 | PREPARE_FOR_SUBMISSION | 1.0 | ✗ | 0 | ⛔ needs build + desc + shots |
## Remaining actions
1. **Boomer Calc** (1.0.1) — submit-ready per `--ready`. **Just click "Add for Review" → Submit** in ASC (Steve-gated).
2. **GovArbitrage** — submit-ready per `--ready`. **Just click "Add for Review" → Submit.** Paste kit if any field is thin: `~/Projects/govarbitrage/apps/mobile/ASC-PASTE-KIT.md`.
3. **Costa Rica** (appId 6799240433) — `--ready` reports `needs build+desc+shots`: description empty, 0 screenshots in ASC, no attached build. A peer node is staging screenshots + description now. Once staged: attach build → paste listing → upload shots → Submit (Steve-gated).
## Changes since Aug 8
- **Homes on Spec** moved PREPARE_FOR_SUBMISSION → **WAITING_FOR_REVIEW** — it got submitted (was previously blocked on attach-build + desc + shots).
- **Boomer Calc** is now **1.0.1 submit-ready** (was showing as already-in-queue at 1.0 on the Aug 8 board; live `--ready` now reports it PREPARE_FOR_SUBMISSION 1.0.1 / submit-ready).
- **67 Calc** was pulled → now **DEVELOPER_REJECTED** — an intentional Guideline 4.3 (duplicate) pull. It is deliberately left dead and is NOT counted as a submit candidate (the Aug 8 board still listed it "in queue" / a 4.3 decision pending).
- Net buckets: **5 in review / 2 submit-ready / 1 intentionally dead / 1 needs-prep** (was 6 in queue / 1 submit-ready / 2 blocked on Aug 8).
## Tooling note (found, not fixed — out of read-only scope)
`ipa-status --ready` and a naive `appStoreVersions[0]` both mis-report apps as "needs build+desc+shots" because ASC returns **multiple duplicate `1.0` version records** per app (empty PREPARE_FOR_SUBMISSION drafts alongside the real populated/submitted version). This board reads the furthest-along version. A durable fix for the `ipa-status` skill would be to select the max-state version rather than the first — flagged for a follow-up (code change, Steve-gated).