Skip to content

Fix ASC skills crashing on gzip-encoded iris responses - #29

Open
kody-w wants to merge 1 commit into
blitzdotdev:masterfrom
kody-w:pr/asc-skill-gzip
Open

kody-w wants to merge 1 commit into
blitzdotdev:masterfrom
kody-w:pr/asc-skill-gzip

Conversation

@kody-w

@kody-w kody-w commented Oct 15, 2026

Copy link
Copy Markdown

Problem

App Store Connect's iris web API can answer with a gzip-encoded body. The asc-team-key-create and asc-iap-attach skills read the response as plain text, so they crash on a gzipped response. When creating an API key, the crash happened after the key was created, which left an extra key behind.

Fix

Decode gzip-encoded iris responses before parsing them in both skills (src/resources/skills/asc-team-key-create/SKILL.md, src/resources/skills/asc-iap-attach/SKILL.md).

Testing

Running in a local build of 1.0.35 since 2026-10-14: key creation completed without the crash. No automated test covers the skill text.

🤖 Generated with Claude Code

App Store Connect's iris API can return gzip-compressed bodies even when
the request doesn't ask for them, and urllib does not decompress. The
skill scripts called resp.read().decode() and crashed with
"UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b". For
asc-team-key-create the crash came after the key was created, so the
agent lost the key ID and a rerun created a duplicate.

- Add a read_body() helper to every inline script in asc-team-key-create,
  asc-app-create-ui and asc-iap-attach, and use it for both success and
  HTTPError bodies.
- asc-team-key-create: document recovering a key that was created when
  the script failed, instead of re-running it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant