apple creative-assets: a placement App Store Connect refuses on the live version is reported with the live version page's deep link, the live page stays unchanged (new placement first, old one removed after) and the other live slots are not retried; pitfall 76

This commit is contained in:
CRTkafa 2026-10-20 02:50:09 +07:00
parent 98d3bf4410
commit 1736300784
4 changed files with 42 additions and 5 deletions

View file

@ -930,8 +930,11 @@ that fails without the fix (see CONTRIBUTING.md).
asset with the same MD5, select it once processed, never re-upload a rejected file or one that failed processing
twice. Then `--add-for-review` puts the unreviewed assets into the draft submission (with the first version, or alone
once the app has an approved version) and `--verify` reads every slot back. With no editable version the live version
is used and only APPROVED assets go onto it; the rest wait for their own review. Uploading, selecting and adding to the
is used and only APPROVED assets go onto it; the rest wait for their own review. Whether the API accepts a new
placement on a live version is not documented: storebound places the new asset first and removes the old one only
after Apple accepted it, and on a 4xx it says so, leaves the live page unchanged, gives the live version page's deep
link (select it there, or create a version and re-run) and does not try the remaining live slots. Uploading, selecting and adding to the
draft are normal steps, not owner buttons; Submit for Review stays the owner's.
- **Guard:** `cli/apple/creative-assets.ts` (`classify`, `pickAsset`, `processingTiming`), `tests/creative-assets.test.ts`
(fake App Store Connect: upload and select in one run, still processing, rejected / archived files, add-for-review
without submitting, verify read-only); the fake commits library assets to PREPARE_FOR_SUBMISSION, as Apple does.
without submitting, verify read-only, a refused live placement); the fake commits library assets to PREPARE_FOR_SUBMISSION, as Apple does.