asc-beta-review
Manage beta app review submissions and review contact details for TestFlight external testing using the `asc` CLI tool. Use this skill when: (1) Submitting a build for beta app review: "asc beta-review submissions create --build-id ID" (2) Checking beta review submission status: "asc beta-review submissions list --build-id ID" (3) Getting a specific submission: "asc beta-review submissions get --submission-id ID" (4) Getting beta review contact details: "asc beta-review detail get --app-id ID" (5) Updating beta review contact info or demo account: "asc beta-review detail update --detail-id ID ..." (6) Managing the per-locale **Beta App Description** and feedback metadata shown to TestFlight testers: "asc beta-app-localizations {list,get,create,update,delete}" (7) User says "submit for beta review", "TestFlight review", "beta review status", "beta review contact", "external testing review", "beta app description", "TestFlight description", or any beta app review task
How do I install this agent skill?
npx skills add https://github.com/tddworks/asc-cli-skills --skill asc-beta-reviewIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides instructions and examples for using the 'asc' CLI tool to manage App Store Connect beta reviews. It follows standard security practices for developer tools, such as referencing local key paths for authentication and reading project configuration from local JSON files.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- Runlayerpass
1/1 file flagged
What does this agent skill do?
Beta App Review with asc
Submit builds for TestFlight external testing review and manage beta review contact details. Apple requires beta app review before distributing builds to external testers via TestFlight.
Authentication
Set up credentials before any beta review commands:
asc auth login --key-id <id> --issuer-id <id> --private-key-path ~/.asc/AuthKey.p8
CAEOAS — Affordances Guide Next Steps
Every JSON response includes "affordances" with ready-to-run commands:
BetaAppReviewSubmission affordances:
{
"id": "sub-abc123",
"buildId": "build-42",
"state": "WAITING_FOR_REVIEW",
"affordances": {
"getSubmission": "asc beta-review submissions get --submission-id sub-abc123",
"listSubmissions": "asc beta-review submissions list --build-id build-42"
}
}
BetaAppReviewDetail affordances:
{
"id": "d-xyz789",
"appId": "app-1",
"contactFirstName": "John",
"contactEmail": "john@example.com",
"demoAccountRequired": false,
"affordances": {
"getDetail": "asc beta-review detail get --app-id app-1",
"updateDetail": "asc beta-review detail update --detail-id d-xyz789"
}
}
Nil optional fields (contactFirstName, contactLastName, contactPhone, contactEmail, demoAccountName, demoAccountPassword, notes) are omitted from JSON output.
Commands
submissions list — list beta review submissions for a build
asc beta-review submissions list --build-id <BUILD_ID> [--pretty]
submissions create — submit a build for beta review
asc beta-review submissions create --build-id <BUILD_ID> [--pretty]
Creates a new beta app review submission. The build enters WAITING_FOR_REVIEW state.
submissions get — get a specific submission
asc beta-review submissions get --submission-id <SUBMISSION_ID> [--pretty]
detail get — get beta review contact details for an app
asc beta-review detail get --app-id <APP_ID> [--pretty]
Returns the beta app review detail record (contact info and demo account) for the app. Each app has one beta review detail record.
detail update — update beta review contact details
asc beta-review detail update --detail-id <DETAIL_ID> \
[--contact-first-name <name>] \
[--contact-last-name <name>] \
[--contact-phone <phone>] \
[--contact-email <email>] \
[--demo-account-name <username>] \
[--demo-account-password <password>] \
[--demo-account-required] \
[--notes <text>]
Only supplied flags are sent — unspecified fields are left unchanged.
Beta App Localizations — asc beta-app-localizations
Per-locale Beta App Description, tester feedback email, marketing URL, and privacy policy URL shown to TestFlight testers. Required by Apple before opening external testing — a missing/empty description for the primary locale is the most common reason an external-testing submission is rejected.
Distinct from the existing commands:
asc beta-review detail→ app-level review contact info + demo accountasc builds update-beta-notes→ per-build "What to Test" notesasc beta-app-localizations→ per-locale beta app description (this section)
# List existing beta localizations for an app
asc beta-app-localizations list --app-id <APP_ID> [--pretty]
# Get a single localization
asc beta-app-localizations get --localization-id <ID>
# Create a new localization (Apple auto-creates one for the primary locale)
asc beta-app-localizations create \
--app-id <APP_ID> \
--locale en-US \
[--description <text>] \
[--feedback-email <email>] \
[--marketing-url <url>] \
[--privacy-policy-url <url>] \
[--tv-os-privacy-policy <text>]
# Patch — only supplied flags are sent; omitted fields unchanged
asc beta-app-localizations update \
--localization-id <ID> \
[--description <text>] \
[--feedback-email <email>] \
[--marketing-url <url>] \
[--privacy-policy-url <url>]
# Delete (e.g. removing a no-longer-supported locale)
asc beta-app-localizations delete --localization-id <ID>
Affordances on each localization: delete, get, listSiblings (asc beta-app-localizations list --app-id <appId>), update.
See docs/features/beta-app-localizations.md for the full reference.
BetaReviewState
| State | Description |
|---|---|
WAITING_FOR_REVIEW | Submitted, waiting for Apple review |
IN_REVIEW | Currently being reviewed |
APPROVED | Approved for external testing |
REJECTED | Rejected — fix issues and resubmit |
Semantic booleans: isPending, isInReview, isApproved, isRejected.
Typical Workflow
APP_ID=$(cat .asc/project.json 2>/dev/null | jq -r '.appId // empty')
# 1. Upload a build
asc builds upload --file MyApp.ipa
# 2. Add the build to an external beta group
BUILD_ID=$(asc builds list --app-id "$APP_ID" | jq -r '.data[0].id')
GROUP_ID=$(asc testflight groups list --app-id "$APP_ID" | jq -r '.data[] | select(.isInternalGroup == false) | .id' | head -1)
asc builds add-beta-group --build-id "$BUILD_ID" --beta-group-id "$GROUP_ID"
# 3. Set up beta review contact details (first time)
asc beta-review detail get --app-id "$APP_ID" --pretty
DETAIL_ID=$(asc beta-review detail get --app-id "$APP_ID" | jq -r '.data[0].id')
asc beta-review detail update --detail-id "$DETAIL_ID" \
--contact-first-name "John" \
--contact-last-name "Doe" \
--contact-email "john@example.com" \
--contact-phone "+1-555-0100"
# 4. Set the Beta App Description for the primary locale (required for external testing)
EXISTING=$(asc beta-app-localizations list --app-id "$APP_ID" | jq -r '.data[] | select(.locale == "en-US") | .id')
if [ -z "$EXISTING" ]; then
asc beta-app-localizations create --app-id "$APP_ID" --locale en-US \
--description "Welcome to the beta — please test the new dashboard." \
--feedback-email beta@example.com
else
asc beta-app-localizations update --localization-id "$EXISTING" \
--description "Welcome to the beta — please test the new dashboard." \
--feedback-email beta@example.com
fi
# 5. Submit the build for beta app review
asc beta-review submissions create --build-id "$BUILD_ID" --pretty
# 6. Check submission status
asc beta-review submissions list --build-id "$BUILD_ID" --pretty
Key Computed Properties (BetaAppReviewDetail)
| Property | Logic |
|---|---|
hasContact | contactEmail != nil && contactPhone != nil |
demoAccountConfigured | !demoAccountRequired || (name != nil && password != nil) |
Resolve App ID
See project-context.md — check .asc/project.json before asking the user or running asc apps list.
Output Flags
--pretty # Pretty-print JSON
--output table # Table format
--output markdown # Markdown table
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/tddworks/asc-cli-skills/asc-beta-review">View asc-beta-review on skillZs</a>