Get the FREE Ultimate OpenClaw Setup Guide →

asc-crash-triage

Scanned
npx machina-cli add skill rudrankriyam/app-store-connect-cli-skills/asc-crash-triage --openclaw
Files (1)
SKILL.md
3.1 KB

asc crash triage

Use this skill to fetch, analyze, and summarize TestFlight crash reports, beta feedback, and performance diagnostics.

Workflow

  1. Resolve the app ID if not provided (use asc apps list).
  2. Fetch data with the appropriate command.
  3. Parse JSON output and present a human-readable summary.

TestFlight crash reports

List recent crashes (newest first):

  • asc crashes --app "APP_ID" --sort -createdDate --limit 10
  • Filter by build: asc crashes --app "APP_ID" --build "BUILD_ID" --sort -createdDate --limit 10
  • Filter by device/OS: asc crashes --app "APP_ID" --device-model "iPhone16,2" --os-version "18.0"
  • All crashes: asc crashes --app "APP_ID" --paginate
  • Table view: asc crashes --app "APP_ID" --sort -createdDate --limit 10 --output table

TestFlight beta feedback

List recent feedback (newest first):

  • asc feedback --app "APP_ID" --sort -createdDate --limit 10
  • With screenshots: asc feedback --app "APP_ID" --sort -createdDate --limit 10 --include-screenshots
  • Filter by build: asc feedback --app "APP_ID" --build "BUILD_ID" --sort -createdDate
  • All feedback: asc feedback --app "APP_ID" --paginate

Performance diagnostics (hangs, disk writes, launches)

Requires a build ID. Resolve via asc builds latest --app "APP_ID" --platform IOS or asc builds list --app "APP_ID" --sort -uploadedDate --limit 5.

  • List diagnostic signatures: asc performance diagnostics list --build "BUILD_ID"
  • Filter by type: asc performance diagnostics list --build "BUILD_ID" --diagnostic-type "HANGS"
    • Types: HANGS, DISK_WRITES, LAUNCHES
  • Get logs for a signature: asc performance diagnostics get --id "SIGNATURE_ID"
  • Download all metrics: asc performance download --build "BUILD_ID" --output ./metrics.json

Resolving IDs

  • App ID from name: asc apps list --name "AppName" or asc apps list --bundle-id "com.example.app"
  • Latest build ID: asc builds latest --app "APP_ID" --platform IOS
  • Recent builds: asc builds list --app "APP_ID" --sort -uploadedDate --limit 5
  • Set default: export ASC_APP_ID="APP_ID"

Summary format

When presenting results, organize by severity and frequency:

  1. Total count — how many crashes/feedbacks in the result set.
  2. Top crash signatures — group by exception type or crash reason, ranked by count.
  3. Affected builds — which build versions are impacted.
  4. Device & OS breakdown — most affected device models and OS versions.
  5. Timeline — when crashes started or spiked.

For performance diagnostics, highlight the highest-weight signatures first.

Notes

  • Default output is JSON; use --output table or --output markdown for quick human review.
  • Use --paginate to fetch all pages when doing a full analysis.
  • Use --pretty with JSON for debugging command output.
  • Crash data from App Store Connect may have 24-48h delay.

Source

git clone https://github.com/rudrankriyam/app-store-connect-cli-skills/blob/main/skills/asc-crash-triage/SKILL.mdView on GitHub

Overview

asc-crash-triage fetches, analyzes, and summarizes TestFlight crash reports, beta feedback, and performance diagnostics. It guides you to resolve app IDs, pull data with asc commands, and present a structured, severity-aware summary.

How This Skill Works

Workflow: resolve the APP_ID if missing using asc apps list, fetch data with the appropriate asc commands (crashes, feedback, or performance diagnostics), then parse the JSON output and present a human-readable, severity-organized summary including total counts, top signatures, affected builds, device/OS breakdown, and timeline.

When to Use It

  • When investigating TestFlight crashes or crash reports reported by beta testers
  • When triaging recent beta tester feedback and identifying recurring issues
  • When diagnosing performance issues such as hangs, disk writes, or launches
  • When you need a crash/diagnostic summary for a specific build or app
  • When you want to identify which builds and devices are affected and view a timeline

Quick Start

  1. Step 1: Resolve APP_ID with asc apps list --name "AppName" or set ASC_APP_ID
  2. Step 2: Fetch data, e.g. asc crashes --app "APP_ID" --sort -createdDate --limit 10
  3. Step 3: Parse JSON and present a severity-organized summary; use --paginate or --output table as needed

Best Practices

  • Resolve APP_ID before querying; use asc apps list or set ASC_APP_ID as a default
  • For diagnostics, first determine the latest or relevant build with asc builds latest or asc builds list
  • Use --paginate to fetch all pages for a complete analysis
  • Use --output table for quick human review or --pretty for debugging JSON; default is JSON
  • Be mindful of data delay: crash data from App Store Connect may have 24-48h delay

Example Use Cases

  • Pull latest crashes for APP_ID and report the top 5 crash signatures with affected devices
  • Fetch beta feedback for a specific build and surface issues with screenshots when available
  • List performance diagnostics for BUILD_ID and download metrics to metrics.json
  • Identify which builds show a spike in HANGS signatures and the devices most affected
  • Generate a JSON summary with total counts, top crash signatures, affected builds, and device/OS breakdown

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers ↗