← back to dashboard

blind-bag-spells (FunSpellPanda) — fleet issue

_Last refreshed: 2026-06-12 (ASC truth generated 2026-06-11T20:30:04Z)._

Status (one line)

Unhealthy because App Store version 1.0.0 is REJECTED with unresolved issues in App Review; the fleet did not auto-heal it because this is an App Store Connect review/policy outcome, not a fixable build/signing defect — diagnosis Not auto-healing (fixable=false, autoHeal=true), verify verdict {"app":"blind-bag-spells","isRealFix":false,"confidence":"high","reasoning":"No fix attempted","risks":""}.

Root cause & evidence

The uploaded binary is healthy — build 10 is VALID. The unhealthy signal comes entirely from App Review, not from the build/upload pipeline. The blocking failure is the ASC review state, which a rebuild cannot clear.

Failing log line (from state/asc-review.json → apps.blind-bag-spells.checks[0].message):

Latest review submission has unresolved issues in App Review

Full check context (state/asc-review.json → apps.blind-bag-spells):

{
  "reviewState": "UNRESOLVED_ISSUES",
  "nextAction": "Resolve the outstanding App Review issues in App Store Connect, then resubmit if needed.",
  "summary": { "errors": 1, "warnings": 0, "infos": 1, "blocking": 1 },
  "submission": {
    "id": "9f71bdba-9903-49dc-9495-dfcb6279e65c",
    "state": "UNRESOLVED_ISSUES",
    "submittedDate": "2026-04-27T15:07:21.108Z"
  },
  "checks": [
    {
      "severity": "error",
      "message": "Latest review submission has unresolved issues in App Review",
      "remediation": "Resolve the outstanding App Review issues in App Store Connect, then resubmit if needed.",
      "field": null
    }
  ]
}

Corroborating fleet truth:

  ** ARCHIVE SUCCEEDED **
  ** EXPORT SUCCEEDED **
  UPLOAD SUCCEEDED with no errors
  [03:15:51] build + upload OK (build 10)
  [03:15:52] done
  [03:15:01] no new changes since last build (eac16bc64a79a65f5981ccd8baa85a2e754d9a44); skipping

i.e. the source repo has not changed, so the fleet has nothing new to build and the rejection persists untouched.

Why the fleet correctly did not auto-heal

autoHeal=true means the fleet *would* re-bump / rebuild / re-upload if there were a fixable build-artifact problem. fixable=false is correct here: the binary is already VALID, so re-running build/upload cannot clear an App Review rejection. Apple's reviewer flagged a content/metadata/behavior issue that requires a human decision and an explicit resubmission — outside the fleet's automated remit. Re-bumping the build number would only burn build numbers without addressing the rejection reason. Hence isRealFix=false, reasoning "No fix attempted".

Claude-ready fix prompt

> Resolve the App Review rejection for blind-bag-spells (ASC name FunSpellPanda, bundle com.zhouzhengxi.blindbagspells, asc_id 6763868165, version 1.0.0, scheme FunSpellPanda, build tool make).
>
> 1. Open App Store Connect → My Apps → FunSpellPanda → version 1.0.0 → App Review / Resolution Center (review submission 9f71bdba-9903-49dc-9495-dfcb6279e65c, submitted 2026-04-27, state UNRESOLVED_ISSUES), and read the exact rejection reason(s). The fleet only records the state, not the reviewer text — state/asc-review.json does not capture the cited guideline. Capture the guideline number(s) and the reviewer's message.
> 2. Decide the fix per the rejection category:
> - Metadata / screenshots / description / age rating / privacy → no rebuild needed. Update the offending fields in ASC (or via fastlane deliver from /Users/zzxwill/Programming/go/src/zzxwill/apple-apps/apps/blind-bag-spells/fastlane), reply in Resolution Center, then resubmit the existing build 10.
> - App behavior / crash / missing functionality / guideline content → fix the app source at /Users/zzxwill/Programming/go/src/zzxwill/apple-apps/apps/blind-bag-spells (Xcode project BlindBagSpells.xcodeproj, sources under BlindBagSpells/, scheme FunSpellPanda, Makefile drives archive/export/upload). Make the code/asset change, commit, then let the fleet (or make) bump build 10 → 11, archive, upload, and resubmit.
> 3. After resolving, resubmit for review in ASC (reply to the reviewer in Resolution Center if a reply is requested). Then refresh fleet truth (ASC sync) so state/asc.json, state/asc-review.json, and state/asc-live.json reflect WAITING_FOR_REVIEW (then READY_FOR_SALE) and the dashboard turns healthy.
> 4. Do NOT auto-bump or rebuild before reading the actual rejection reason — if it is metadata-only, a rebuild wastes a build number and does not clear the rejection.

Relevant paths:

Last known-good build number

From state/asc.json → blind-bag-spells: build 10 (latest_build_state: "VALID", build_count: 10, uploaded 2026-05-23T12:16:27-07:00). The binary is valid; only the App Review submission is rejected. A new build is needed only if the rejection is a behavior/content defect — for metadata-only rejections, resubmit build 10 as-is.

Notes