sincecutoff.com
← all changes

eas testflight feedback and crash-report commands

Introduced 2026-07-27 · score 0.96

HOW TO USE IT

When debugging an iOS app, use `eas testflight:feedback` to inspect tester comments, device details, and screenshot URLs, or `eas testflight:crashes` to inspect crashes and full crash logs.

eas testflight:feedback [<submission-id-or-app-store-connect-url>] [--offset <value>] [--limit <value>] [--json]
eas testflight:crashes [<submission-id-or-app-store-connect-url>] [--offset <value>] [--limit <value>] [--json]

WHY THIS HELPS

Inspect TestFlight tester feedback or crash reports while debugging an iOS app.

REQUIREMENTS AND LIMITATIONS

  • Version: v21.3.0
  • [ID]: ID or App Store Connect API URL of a single submission; workflow triggers expose `app_store_connect.beta_feedback.id` and `.url`.
  • --offset: Starting index for pagination; defaults to 0.
  • --limit: Items fetched per query; defaults to 20 and is capped at 200.
  • --json: Enables JSON output; non-JSON messages go to stderr and the flag implies non-interactive mode.
  • --profile: Submit profile from `eas.json` used to resolve the bundle identifier and App Store Connect API key; defaults to `production`.
  • --type: Kind of feedback the ID refers to (`crash` or `screenshot`); only needed with a bare ID for screenshot feedback on `crashes` or crash feedback on `feedback`. A URL encodes the type.
  • Prerequisite: Install EAS CLI (`npm install -g eas-cli` or `yarn global add eas-cli`).
  • Data is read from App Store Connect.
  • Single-submission lookup accepts an ID or the App Store Connect URL exposed by EAS workflow triggers.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card