asc-iap-attach

Attach in-app purchases and subscriptions to an App Store Connect version for review.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-iap-attach-dustinober1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-iap-attach
Source: https://github.com/dustinober1/sundee-fundee-ios/tree/main/SundeeFundeeApp/.agents/skills/asc-iap-attach
Command: npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-iap-attach-dustinober1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Apple's public App Store Connect API cannot attach in-app purchases or subscriptions to a version for first-time submissions, returning FIRST_SUBSCRIPTION_MUST_BE_SUBMITTED_ON_VERSION errors. This Skill uses the internal iris API with a cached web session to perform the same attachment the App Store Connect web UI does. ## Core Features & Use Cases - List Monetization Items: Enumerate subscription groups, subscriptions, and in-app purchases with their state and attachment status for a given app ID. - Attach Subscriptions and IAPs: Submit subscriptionSubmissions and inAppPurchaseSubmissions with the submitWithNextAppStoreVersion attribute via the iris API. - Session Recovery: Detect expired sessions (401 responses) and re-authenticate through the asc_web_auth MCP tool, then retry. - Use Case: You are submitting a new app version and your subscriptions are in Ready to Submit state but cannot be attached through the public API. This Skill lists the items, attaches them, and refreshes the submission readiness checklist. ## Quick Start Attach all Ready to Submit in-app purchases and subscriptions to my current App Store Connect app version for review.

Frequently Asked Questions about asc-iap-attach

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I attach in-app purchases to an App Store Connect version?▼

List your IAPs and subscriptions via the iris API to find items in Ready to Submit state, then POST subscriptionSubmissions or inAppPurchaseSubmissions with submitWithNextAppStoreVersion set to true. This mirrors the checkbox action in the App Store Connect web UI.

Why does the App Store Connect API return FIRST_SUBSCRIPTION_MUST_BE_SUBMITTED_ON_VERSION?▼

The public App Store Connect API does not support attaching subscriptions or IAPs to a version for first-time submissions, and reviewSubmissionItems lacks those relationship types. The internal iris API supports the submitWithNextAppStoreVersion attribute needed for this.

What happens if the App Store Connect web session expires?▼

The iris API returns a 401 Not Authorized error when the session expires. Call the asc_web_auth MCP tool to open the Apple ID login window, complete login and 2FA, and the session file is refreshed automatically so you can retry.

Does attaching a subscription twice cause an error?▼

No. If the subscription is already attached, the iris API returns HTTP 409 with a message that it is already set to submit with the next App Store version. This response is safe to treat as success.

What are the prerequisites for attaching IAPs to an app version?▼

You need a valid web session file, your app ID, IAPs or subscriptions already created in Ready to Submit state, and a build uploaded and attached to the current app version. Requests to the iris API should be spaced at least 350ms apart.