Asc Crash Triage

by rorkai9c7e769f09a1No license1K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 3 days ago

Triage TestFlight crashes, beta feedback, and performance diagnostics using asc. Use when the user asks about TF crashes, TestFlight crash reports, beta tester feedback, app hangs, disk writes, launch diagnostics, or wants a crash summary for a build or app.

Instructions onlyDevOps & Cloud
AI-generated overview

Triages TestFlight crashes, beta feedback, and performance diagnostics via the asc CLI, summarizing findings by severity and frequency.

What it does
This skill guides an agent through fetching TestFlight crash reports, beta tester feedback, and performance diagnostics (hangs, disk writes, launches) using the asc command-line tool. It covers resolving app and build IDs, filtering by build, device, or OS, and paginating results. It then instructs the agent to parse the JSON output and present a human-readable summary organized by total count, top crash signatures, affected builds, device and OS breakdown, and timeline.
When to use it
Use it when a user asks about TestFlight crashes, beta tester feedback, app hangs, disk writes, launch diagnostics, or wants a crash summary for a specific build or app.
Requirements
Requires the asc CLI to be available and authenticated with App Store Connect access, plus network access to fetch data. It ships no scripts; it is instructions only. Crash data may lag 24-48 hours.

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 testflight crashes list --app "APP_ID" --sort -createdDate --limit 10
  • Filter by build: asc testflight crashes list --app "APP_ID" --build-id "BUILD_ID" --sort -createdDate --limit 10
  • Filter by device/OS: asc testflight crashes list --app "APP_ID" --device-model "iPhone16,2" --os-version "18.0"
  • All crashes: asc testflight crashes list --app "APP_ID" --paginate
  • Table view: asc testflight crashes list --app "APP_ID" --sort -createdDate --limit 10 --output table

TestFlight beta feedback

List recent feedback (newest first):

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

Performance diagnostics (hangs, disk writes, launches)

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

  • List diagnostic signatures: asc performance diagnostics list --build-id "BUILD_ID"
  • Filter by type: asc performance diagnostics list --build-id "BUILD_ID" --diagnostic-type "HANGS"
    • Types: HANGS, DISK_WRITES, LAUNCHES
  • View logs for a signature: asc performance diagnostics view --id "SIGNATURE_ID"
  • Download all metrics: asc performance download --build-id "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 info --app "APP_ID" --latest --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 and attribution

Source:rorkai/app-store-connect-cli-skillsinskills/asc-crash-triageat commit9c7e769

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal