mirror of
https://github.com/rudrankriyam/App-Store-Connect-CLI.git
synced 2026-04-25 07:35:48 +03:00
[GH-ISSUE #505] API associatedErrors not displayed to user, making submission errors opaque #140
Labels
No labels
bug
bug
documentation
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/App-Store-Connect-CLI#140
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @yspreen on GitHub (Feb 11, 2026).
Original GitHub issue: https://github.com/rudrankriyam/App-Store-Connect-CLI/issues/505
Originally assigned to: @rudrankriyam on GitHub.
Summary
When the App Store Connect API returns error responses containing
meta.associatedErrors,asconly displays the top-level error message and discards the associated errors — which often contain the actual actionable information.Reproduction
PREPARE_FOR_SUBMISSIONstate that's missing some of the newer required age rating fields (e.g.parentalControls,advertising,healthOrWellnessTopics, etc.)ascdisplays:The error message literally says "check associated errors" but
ascdoesn't show them.What the API actually returns
The 409 response body (3471 bytes) contains a
meta.associatedErrorsobject with the full details:Expected behavior
ascshould display the associated errors, e.g.:Impact
This turned a 30-second fix (
asc age-rating setwith the missing fields) into a 20+ minute debugging session that required writing a custom JWT-signing script to call the raw API. The--api-debugflag only shows headers and status codes, not response bodies, so there's no workaround withinascitself.Environment
ascversion: 0.26.3@rudrankriyam commented on GitHub (Feb 11, 2026):
I am sorry; I faced this as well but did not do anything about it. Fixing asap
@yspreen commented on GitHub (Feb 11, 2026):
no worries at all this issue was submitted by claude. no human time lost. I told claude to open an issue with the
ghcommand, it found a workaround by using the p8 files itself to call the api that's how the bug was surfaced. thanks for building a great tool!btw I installed the skill by manually copying the skills from the repo into my .claude folder. is there a better way? maybe one that auto-updates if the repo changes? a claude plugin or something? I'm kinda new to skills
@rudrankriyam commented on GitHub (Feb 11, 2026):
The CLI itself has command for it, check it out!
@yspreen commented on GitHub (Feb 11, 2026):
nice! is there a command to update it? and/or auto-add any new skills that might be added to the repo?
@rudrankriyam commented on GitHub (Feb 11, 2026):
#506 fixes this
@rudrankriyam commented on GitHub (Feb 11, 2026):
asc install skillsworks as both install + update (re-run it anytime)