CLI reference

Commands, arguments, flags and examples below are generated from the CLI definitions. Run flightline <command> --help to check your installed version. Placeholders such as <bundleId> must be replaced with your own values.

Global options

These options are inherited by subcommands unless overridden.

Command groups

accessibility-declarations

Manage per-device accessibility declarations

Usage

flightline accessibility-declarations [flags]

accessibility-declarations create

Create a declaration draft with explicit support answers

Usage

flightline accessibility-declarations create <bundleId> [flags]

accessibility-declarations delete

Delete a draft declaration

Usage

flightline accessibility-declarations delete <declarationId> [flags]

accessibility-declarations get

Read one accessibility declaration

Usage

flightline accessibility-declarations get <declarationId> [flags]

accessibility-declarations list

List accessibility declarations for an app

Usage

flightline accessibility-declarations list <bundleId> [flags]

accessibility-declarations publish

Publish a draft declaration

Usage

flightline accessibility-declarations publish <declarationId> [flags]

accessibility-declarations update

Update explicit support answers on a draft

Usage

flightline accessibility-declarations update <declarationId> [flags]

age-rating

age-rating reads the questionnaire Apple uses to compute a version's age rating. The declaration lives on the per-version appInfo resource; Flightline resolves bundleId + versionString to the right appInfo and fetches its ageRatingDeclaration. L3 preflight will flag declarations with unanswered questions: surface the same data here for manual inspection.

Usage

flightline age-rating [flags]

age-rating get

Get the age-rating declaration for a version

Usage

flightline age-rating get <bundleId> [flags]

Examples

flightline age-rating get com.example.myapp --version 1.0.1
  flightline age-rating get com.example.myapp --version 1.0.1 --output json | jq .attributes

age-rating set

set PATCHes the age-rating declaration for a version with the answers loaded from --from. Accepts JSON (.json) or YAML (.yaml/.yml). Top-level keys must match Apple's wire names (e.g. alcoholTobaccoOrDrugUseOrReferences: NONE). Idempotent: the file is diffed against the current declaration; only fields that actually differ go in the PATCH body. When everything already matches, returns noop=true without issuing a PATCH. Validation: every key must be a recognized field on the declaration; an unknown key surfaces as a typed error naming the offending key. Frequency enums must be one of NONE | INFREQUENT_OR_MILD | FREQUENT_OR_INTENSE | INFREQUENT | FREQUENT. Boolean fields must be true/false.

Usage

flightline age-rating set <bundleId> [flags]

Examples

flightline age-rating set com.example.myapp --version 1.0.1 --from age-rating.yaml
  flightline age-rating set com.example.myapp --version 1.0.1 --from age-rating.json --output json

analytics

analytics drives Apple's asynchronous analytics report lifecycle: 1. request : submit an analyticsReportRequests entry to Apple 2. status : refresh Apple state and update the persisted checkpoint 3. list-instances: enumerate report instances for the active request 4. download: pull every segment of an instance to local CSV files State persists to $XDG_STATE_HOME/flightline//analytics.json so a Ctrl-C between submit and download resumes cleanly on the next run.

Usage

flightline analytics [flags]

analytics download

Download every segment of an analytics report instance

Usage

flightline analytics download <bundleId> [flags]

Examples

flightline analytics download com.example.myapp --instance INST-1
  flightline analytics download com.example.myapp --instance INST-1 --out ./reports/

analytics list-instances

List instances of analytics reports for the active request

Usage

flightline analytics list-instances <bundleId> [flags]

Examples

flightline analytics list-instances com.example.myapp
  flightline analytics list-instances com.example.myapp --report-id RPT-1
  flightline analytics list-instances com.example.myapp --category APP_USAGE --name-contains daily

analytics request

Submit a new analytics report request

Usage

flightline analytics request <bundleId> [flags]

Examples

flightline analytics request com.example.myapp --access-type ONE_TIME_SNAPSHOT
  flightline analytics request com.example.myapp --access-type ONE_TIME_SNAPSHOT --wait
  flightline analytics request com.example.myapp --access-type ONGOING --wait --max-duration 10m

analytics status

Refresh and show state for an analytics request

Usage

flightline analytics status <bundleId> [flags]

Examples

flightline analytics status com.example.myapp
	  flightline analytics status com.example.myapp --refresh=false
	  flightline analytics status com.example.myapp --output json | jq .requestId

app-availability

Inspect app availability by territory

Usage

flightline app-availability [flags]

app-availability get

Show availability, pre-order state, and blockers for every territory

Usage

flightline app-availability get <bundleId> [flags]

app-availability preorders

Manage explicit app pre-order actions

Usage

flightline app-availability preorders [flags]

app-availability preorders end

End active pre-orders for the selected territories and release the app immediately. This action cannot be reconciled through state apply. Flightline re-reads each selected territory and requires an active pre-order before sending the request.

Usage

flightline app-availability preorders end <bundleId> [flags]

app-eula

Inspect and manage the custom app EULA

Usage

flightline app-eula [flags]

app-eula delete

Delete the app's custom EULA

Usage

flightline app-eula delete <bundleId> [flags]

app-eula get

Show the observed custom EULA and complete territory set

Usage

flightline app-eula get <bundleId> [flags]

app-eula set

Create or update the custom EULA from an agreement file and exact territories

Usage

flightline app-eula set <bundleId> [flags]

app-tags

Inspect assigned App Store tags and manage their visibility

Usage

flightline app-tags [flags]

app-tags list

List tags assigned to an app

Usage

flightline app-tags list <bundleId> [flags]

app-tags set-visibility

Set visibility for a tag already assigned to an app

Usage

flightline app-tags set-visibility <bundleId> <tagId> [flags]

apply

Loads <state.yaml>, validates it against the schema, fetches live state, computes the diff, and writes the changes back to ASC. Without --confirm, apply prints the plan and refuses to write: same guardrail as terraform plan. With --confirm, every leaf-level change dispatches to its L1 writer, with a checkpoint persisted after every success so a Ctrl-C / crash mid-apply resumes cleanly via --resume. --dry-run fetches live state and validates every planned dispatch, but sends no mutating API requests. Output lists planned changes, never applied changes. It requires credentials and network access. Examples: flightline apply state.yaml # plan only, refuses to write flightline apply state.yaml --confirm # write changes flightline apply state.yaml --confirm --resume # continue after Ctrl-C flightline apply state.yaml --dry-run --output json

Usage

flightline apply <state.yaml> [flags]

apps

apps groups read commands over the /v1/apps resource.

Usage

flightline apps [flags]

apps get

Get a single app by bundle ID

Usage

flightline apps get <bundleId> [flags]

Examples

flightline apps get com.example.myapp
  flightline apps get com.example.myapp --output json | jq .attributes.name

apps list

List apps visible to the configured ASC key

Usage

flightline apps list [flags]

Examples

flightline apps list
  flightline apps list --output json | jq -r '.apps[].attributes.bundleId'
  flightline apps list --limit 50

beta-feedback

beta-feedback groups read commands over Apple's TestFlight feedback resources: - crash : list crash submissions, optionally filtered by build - screenshot : list screenshot submissions, optionally filtered by build - download : download the crash log or screenshot to disk Feedback is tester-authored, so this command group is read-only.

Usage

flightline beta-feedback [flags]

beta-feedback crash

List TestFlight crash submissions for an app

Usage

flightline beta-feedback crash <bundleId> [flags]

Examples

flightline beta-feedback crash com.example.myapp
	  flightline beta-feedback crash com.example.myapp --build 42
	  flightline beta-feedback crash com.example.myapp --build 2 --version 1.1 --platform IOS
	  flightline beta-feedback crash com.example.myapp --output json | jq '.submissions[].attributes.deviceModel'

beta-feedback download

Download the crash log or screenshot for a feedback submission

Usage

flightline beta-feedback download <feedbackId> [flags]

Examples

flightline beta-feedback download CRASH-1234 --out crash.txt
  flightline beta-feedback download SCREENSHOT-5678 --type screenshot --out shot.png
  flightline beta-feedback download CRASH-1234 --output json

beta-feedback screenshot

List TestFlight screenshot submissions for an app

Usage

flightline beta-feedback screenshot <bundleId> [flags]

Examples

flightline beta-feedback screenshot com.example.myapp
	  flightline beta-feedback screenshot com.example.myapp --build 2 --version 1.1 --platform IOS
	  flightline beta-feedback screenshot com.example.myapp --build 42 --output json

builds

builds groups read commands over the /v1/builds resource.

Usage

flightline builds [flags]

builds attach

Attach a build to an App Store version (idempotent: skip if already attached)

Usage

flightline builds attach <bundleId> [flags]

Examples

flightline builds attach com.example.myapp --version 1.0.1 --build 42
  flightline builds attach com.example.myapp --version 1.0.1 --build 42 --platform IOS --output json

builds get

Get a single build by build number (CFBundleVersion)

Usage

flightline builds get <bundleId> [flags]

Examples

flightline builds get com.example.myapp --build 42
	  flightline builds get com.example.myapp --build 2 --version 1.1 --platform IOS
	  flightline builds get com.example.myapp --build 42 --output json | jq .attributes.processingState

builds list

List builds for an app

Usage

flightline builds list <bundleId> [flags]

Examples

flightline builds list com.example.myapp
  flightline builds list com.example.myapp --limit 20
  flightline builds list com.example.myapp --output json | jq -r '.builds[].version'

categories

categories groups read commands over the /v1/appCategories resource. categories list dumps Apple's catalog of top-level categories. Filterable by --platform; defaults to IOS to match Flightline's default platform. categories get shows the category assignments on the app's editable appInfo (primary + secondary plus their subcategories). Unassigned slots are a frequent rejection cause: surface them visibly.

Usage

flightline categories [flags]

categories get

Show the category assignments on an app's editable appInfo

Usage

flightline categories get <bundleId> [flags]

Examples

flightline categories get com.example.myapp
  flightline categories get com.example.myapp --output json | jq .primaryCategory

categories list

List top-level App Store categories

Usage

flightline categories list [flags]

Examples

flightline categories list
  flightline categories list --platform MAC_OS
  flightline categories list --output json | jq -r '.categories[].id'

categories set

categories set updates an app's primary/secondary category assignments. Apple stores the assignments on the app's editable appInfo as 6 to-one relationships (primaryCategory, primarySubcategoryOne, primarySubcategoryTwo, secondaryCategory, secondarySubcategoryOne, secondarySubcategoryTwo). The categories must come from /v1/appCategories: see flightline categories list. Only flags that are explicitly passed are written; omitted flags are left untouched. To clear a slot pass --clear-secondary or one of its sub-equivalents. Idempotent: the command first reads the current assignments and only PATCHes when at least one requested value differs from current.

Usage

flightline categories set <bundleId> [flags]

Examples

flightline categories set com.example.myapp --primary PRODUCTIVITY --primary-subcat BUSINESS
  flightline categories set com.example.myapp --secondary UTILITIES
  flightline categories set com.example.myapp --clear-secondary
  flightline categories set com.example.myapp --primary GAMES --output json

content-rights

Inspect and set the app content rights declaration

Usage

flightline content-rights [flags]

content-rights get

Show the observed content rights declaration

Usage

flightline content-rights get <bundleId> [flags]

content-rights set

Set an explicit content rights declaration

Usage

flightline content-rights set <bundleId> <declaration> [flags]

custom-product-pages

custom-product-pages groups read commands over Apple's AppCustomProductPage resources: alternate App Store listings used to target ad-driven traffic with different screenshots and descriptions. list : list all configured pages with current state get --page : detail for one page (versions + localizations)

Usage

flightline custom-product-pages [flags]

custom-product-pages create

Create a custom product page (idempotent on name)

Usage

flightline custom-product-pages create <bundleId> [flags]

Examples

flightline custom-product-pages create com.example.myapp --name "Holiday Promo"
  flightline custom-product-pages create com.example.myapp --name "Spring 2026" --output json

custom-product-pages delete

Delete a custom product page (idempotent)

Usage

flightline custom-product-pages delete <pageId> [flags]

Examples

flightline custom-product-pages delete CPP-1

custom-product-pages get

Detail for one custom product page (versions + localizations)

Usage

flightline custom-product-pages get <bundleId> [flags]

Examples

flightline custom-product-pages get com.example.myapp --page 8000000001
  flightline custom-product-pages get com.example.myapp --page 8000000001 --output json

custom-product-pages list

List custom product pages for an app

Usage

flightline custom-product-pages list <bundleId> [flags]

Examples

flightline custom-product-pages list com.example.myapp
  flightline custom-product-pages list com.example.myapp --output json | jq -r '.pages[].attributes.name'

custom-product-pages update

Update a custom product page's mutable attributes (idempotent)

Usage

flightline custom-product-pages update <pageId> [flags]

Examples

flightline custom-product-pages update CPP-1 --visible
  flightline custom-product-pages update CPP-1 --name "Updated Holiday"

diagnostics

diagnostics groups read commands over Apple's diagnostic signatures resource. Apple deduplicates crash and hang reports into signatures: same call stack, same crash, regardless of how many users hit it. Apple v4.5 only exposes diagnostic signatures scoped to a build: - list --build : list signatures for a build - get : fetch the full log payload There is no app-wide aggregation API in v4.5; --build is required on list.

Usage

flightline diagnostics [flags]

diagnostics get

Fetch the full log payload for a diagnostic signature

Usage

flightline diagnostics get <signatureId> [flags]

Examples

flightline diagnostics get DIAG-SIG-1234
  flightline diagnostics get DIAG-SIG-1234 --output json

diagnostics list

List diagnostic signatures for a specific build

Usage

flightline diagnostics list <bundleId> [flags]

Examples

flightline diagnostics list com.example.myapp --build 42
	  flightline diagnostics list com.example.myapp --build 2 --version 1.1 --platform IOS
	  flightline diagnostics list com.example.myapp --build 42 --type HANGS
  flightline diagnostics list com.example.myapp --build 42 --output json | jq '.signatures[].attributes.weight'

events

Manage In-App Events

Usage

flightline events [flags]

events create

Create a draft In-App Event

Usage

flightline events create <bundleId> [flags]

events delete

Delete a draft, archived, or approved In-App Event

Usage

flightline events delete <bundleId> [flags]

events get

Read one owned In-App Event

Usage

flightline events get <bundleId> [flags]

events list

List all In-App Events

Usage

flightline events list <bundleId> [flags]

events localizations

Manage event localizations

Usage

flightline events localizations [flags]

events localizations create

Create a draft event localization

Usage

flightline events localizations create <bundleId> [flags]

events localizations delete

Delete a draft event localization

Usage

flightline events localizations delete <bundleId> [flags]

events localizations get

Read one event localization

Usage

flightline events localizations get <bundleId> [flags]

events localizations list

List every localization for an owned event

Usage

flightline events localizations list <bundleId> [flags]

events localizations update

Update draft event localization text

Usage

flightline events localizations update <bundleId> [flags]

events media

Manage event card and detail images or videos

Usage

flightline events media [flags]

events media delete

Delete one owned draft event image or video

Usage

flightline events media delete <bundleId> [flags]

events media get

Read one owned event image or video

Usage

flightline events media get <bundleId> [flags]

events media list

List all event images and videos in a localization

Usage

flightline events media list <bundleId> [flags]

events media upload

Upload one event card or detail image or video and wait for processing

Usage

flightline events media upload <bundleId> <file> [flags]

events media wait

Wait for existing event media without uploading again

Usage

flightline events media wait <bundleId> [flags]

events propose-submission-item

Check event review readiness and return an item proposal

Usage

flightline events propose-submission-item <bundleId> [flags]

events update

Update a draft In-App Event

Usage

flightline events update <bundleId> [flags]

experiments

Manage App Store product page experiments

Usage

flightline experiments [flags]

experiments create

Create an app-bound v2 experiment

Usage

flightline experiments create <bundleId> [flags]

experiments delete

Delete an unstarted experiment

Usage

flightline experiments delete <bundleId> [flags]

experiments get

Read a selected v2 experiment

Usage

flightline experiments get <bundleId> [flags]

experiments list

List v2 experiments for one version

Usage

flightline experiments list <bundleId> [flags]

experiments proposal

Read a review item proposal; does not attach or submit

Usage

flightline experiments proposal <bundleId> [flags]

experiments start

start a selected experiment

Usage

flightline experiments start <bundleId> [flags]

experiments stop

stop a selected experiment

Usage

flightline experiments stop <bundleId> [flags]

experiments treatments

Manage experiment variants

Usage

flightline experiments treatments [flags]

experiments treatments create

Create a treatment

Usage

flightline experiments treatments create <bundleId> [flags]

experiments treatments delete

Delete an unstarted treatment

Usage

flightline experiments treatments delete <bundleId> [flags]

experiments treatments list

List variants for a selected experiment

Usage

flightline experiments treatments list <bundleId> [flags]

experiments treatments localizations

Manage treatment locales

Usage

flightline experiments treatments localizations [flags]

experiments treatments localizations assets

Manage treatment screenshots and previews

Usage

flightline experiments treatments localizations assets [flags]

experiments treatments localizations assets delete

Delete selected treatment media

Usage

flightline experiments treatments localizations assets delete <bundleId> [flags]

experiments treatments localizations assets list

List all sets and media under a selected treatment locale

Usage

flightline experiments treatments localizations assets list <bundleId> [flags]

experiments treatments localizations assets upload

Upload a treatment screenshot or preview

Usage

flightline experiments treatments localizations assets upload <bundleId> <file> [flags]

experiments treatments localizations assets wait

Wait for selected treatment media processing

Usage

flightline experiments treatments localizations assets wait <bundleId> [flags]

experiments treatments localizations create

Create a treatment locale

Usage

flightline experiments treatments localizations create <bundleId> [flags]

experiments treatments localizations delete

Delete a treatment locale

Usage

flightline experiments treatments localizations delete <bundleId> [flags]

experiments treatments localizations list

List treatment locales

Usage

flightline experiments treatments localizations list <bundleId> [flags]

experiments treatments update

Update treatment name or app icon

Usage

flightline experiments treatments update <bundleId> [flags]

experiments update

Update draft experiment name or traffic

Usage

flightline experiments update <bundleId> [flags]

export-compliance

export-compliance reads Apple's two-tier export-compliance surface: 1. The per-build boolean usesNonExemptEncryption (lives on the Build attached to the version, not on the version itself). 2. The per-app appEncryptionDeclaration resources for full ECCN classification when the boolean is not sufficient. L3 preflight will gate submissions on a missing build-level answer; this verb surfaces the same data for manual inspection.

Usage

flightline export-compliance [flags]

export-compliance get

Get export-compliance state for a version

Usage

flightline export-compliance get <bundleId> [flags]

Examples

flightline export-compliance get com.example.myapp --version 1.0.1
  flightline export-compliance get com.example.myapp --version 1.0.1 --output json | jq .build

export-compliance set

set PATCHes the build attached to a version with the export-compliance boolean Apple requires before review. Apple's two-tier model: 1. Per-build boolean: usesNonExemptEncryption on the Build attached to the version. This verb writes that field. 2. Per-app AppEncryptionDeclaration: for full ECCN classification. The --exempt and --documentation-url flags target this surface and are reserved for a follow-up command; they currently return a typed error. Idempotent: reads the build's current answer; PATCH only when the requested value differs.

Usage

flightline export-compliance set <bundleId> [flags]

Examples

flightline export-compliance set com.example.myapp --version 1.0.1 --uses-encryption false
  flightline export-compliance set com.example.myapp --version 1.0.1 --uses-encryption true --output json

fetch

Pulls every L2 surface Flightline supports for the given bundleId and writes the result as a Flightline state file. Beta build metadata is scoped to the attached build; --include-beta-builds adds complete group membership sets. Default output is YAML with a yaml-language-server schema directive prepended for editor autocomplete. Surfaces absent from the state file are not managed. The diff engine leaves those surfaces untouched on subsequent applies. Examples: flightline fetch app.tideterm.ios > state.yaml flightline fetch app.tideterm.ios -o state.yaml --version 1.0.1 flightline fetch app.tideterm.ios --output json | jq '.spec.version'

Usage

flightline fetch <bundleId> [flags]

finance

finance pulls finance/settlement reports from /v1/financeReports. Apple indexes finance reports by fiscal year/month, not calendar month. Daily granularity belongs to flightline sales. FINANCIAL defaults to the consolidated region ZZ. FINANCE_DETAIL defaults to Z1. The bundleId argument filters typed output by Vendor Identifier so a single- vendor multi-app account stays focused. --output tsv streams Apple's raw wire format unfiltered. Vendor number is read from APP_STORE_CONNECT_VENDOR_NUMBER.

Usage

flightline finance <bundleId> [flags]

Examples

flightline finance com.example.myapp --month 2026-04
	  flightline finance com.example.myapp --month 2026-04 --region US
	  flightline finance com.example.myapp --month 2026-04 --report-type FINANCE_DETAIL
  flightline finance com.example.myapp --month 2026-04 --output json | jq '.summary'
  flightline finance com.example.myapp --month 2026-04 --output tsv > finance.tsv

iap

iap groups read commands over the /v2/inAppPurchases resource. Auto-renewable subscriptions live under a separate /v1/subscriptionGroups resource and are not handled here: see flightline subscriptions.

Usage

flightline iap [flags]

iap commerce

Inspect and set non-subscription IAP pricing and availability

Usage

flightline iap commerce [flags]

iap commerce availability

Inspect IAP territory availability

Usage

flightline iap commerce availability <bundleId> [flags]

iap commerce price-points

List price points for one IAP

Usage

flightline iap commerce price-points <bundleId> [flags]

iap commerce pricing

Inspect complete IAP manual price windows

Usage

flightline iap commerce pricing <bundleId> [flags]

iap commerce set-availability

Set IAP territory availability as an explicit complete set

Usage

flightline iap commerce set-availability <bundleId> [flags]

iap commerce set-price

Set the current IAP base price while preserving manual windows

Usage

flightline iap commerce set-price <bundleId> [flags]

iap create

create reserves a new In-App Purchase under the given app. Idempotent: if an IAP with --product-id already exists for this app, returns the existing record with noop=true rather than failing or creating a duplicate.

Usage

flightline iap create <bundleId> [flags]

Examples

flightline iap create com.example.myapp --product-id com.example.myapp.lifetime --type NON_CONSUMABLE --name "Lifetime Pro"
  flightline iap create com.example.myapp --product-id com.example.myapp.coins --type CONSUMABLE --name Coins --review-note "Currency for the in-app store"

iap delete

delete removes an In-App Purchase. Destructive: requires --yes to confirm. Idempotent: if the IAP doesn't exist, returns noop=true without issuing a DELETE. Apple may refuse deletion of an IAP that has been APPROVED and is visible on the store; that case surfaces as a typed APIError.

Usage

flightline iap delete <bundleId> [flags]

Examples

flightline iap delete com.example.myapp --product com.example.myapp.lifetime --yes

iap get

Get a single in-app purchase by productId

Usage

flightline iap get <bundleId> [flags]

Examples

flightline iap get com.example.myapp --product com.example.myapp.lifetime
  flightline iap get com.example.myapp --product com.example.myapp.lifetime --output json

iap list

List in-app purchases for an app

Usage

flightline iap list <bundleId> [flags]

Examples

flightline iap list com.example.myapp
  flightline iap list com.example.myapp --type CONSUMABLE
  flightline iap list com.example.myapp --output json | jq -r '.iaps[].attributes.productId'

iap localizations

Manage and inspect IAP localizations

Usage

flightline iap localizations [flags]

iap localizations list

List localizations for an in-app purchase

Usage

flightline iap localizations list <bundleId> [flags]

Examples

flightline iap localizations list com.example.myapp --product com.example.myapp.lifetime
  flightline iap localizations list com.example.myapp --product com.example.myapp.lifetime --output json

iap localizations set

set creates the localization for --locale if it does not exist, or PATCHes the mutable fields (name, description) if it does. Idempotent: when the existing localization already matches the supplied flags, returns noop=true.

Usage

flightline iap localizations set <bundleId> [flags]

Examples

flightline iap localizations set com.example.myapp --product com.example.myapp.lifetime --locale en-US --name "Lifetime Pro" --description "Unlock everything, forever."
  flightline iap localizations set com.example.myapp --product com.example.myapp.lifetime --locale fr-FR --name "Pro à vie" --description "Tout débloquer, pour toujours."

iap offer-codes

Inspect and deliberately issue non-subscription IAP offer codes

Usage

flightline iap offer-codes [flags]

iap offer-codes create-custom

Create a custom code batch for an existing offer

Usage

flightline iap offer-codes create-custom <bundleId> [flags]

iap offer-codes create-definition

Create an IAP offer definition with explicit prices

Usage

flightline iap offer-codes create-definition <bundleId> [flags]

iap offer-codes create-one-time

Issue a one-time code batch for an existing offer

Usage

flightline iap offer-codes create-one-time <bundleId> [flags]

iap offer-codes download

Download one-time code values to a new private CSV file

Usage

flightline iap offer-codes download <bundleId> [flags]

iap offer-codes get

Inspect an offer and its complete prices and batches

Usage

flightline iap offer-codes get <bundleId> [flags]

iap offer-codes list

List offer definitions for one IAP

Usage

flightline iap offer-codes list <bundleId> [flags]

iap promotion

Manage non-subscription IAP promotional images and promoted purchases

Usage

flightline iap promotion [flags]

iap promotion images

Manage IAP promotional images

Usage

flightline iap promotion images [flags]

iap promotion images delete

Delete a confirmed promotional image

Usage

flightline iap promotion images delete <bundleId> <productId> <imageId> [flags]

iap promotion images list

List IAP promotional images

Usage

flightline iap promotion images list <bundleId> <productId> [flags]

iap promotion images upload

Upload and process a promotional image

Usage

flightline iap promotion images upload <bundleId> <productId> <file> [flags]

iap promotion images wait

Inspect promotional image processing

Usage

flightline iap promotion images wait <bundleId> <productId> <imageId> [flags]

iap promotion promoted

Manage app promoted purchases

Usage

flightline iap promotion promoted [flags]

iap promotion promoted delete

Delete a confirmed IAP promotion

Usage

flightline iap promotion promoted delete <bundleId> <productId> [flags]

iap promotion promoted list

List promoted purchases

Usage

flightline iap promotion promoted list <bundleId> [flags]

iap promotion promoted order

Set the complete promoted purchase order

Usage

flightline iap promotion promoted order <bundleId> [flags]

iap promotion promoted set

Create or update a confirmed IAP promotion

Usage

flightline iap promotion promoted set <bundleId> <productId> [flags]

iap review-screenshot

Manage IAP App Store review screenshots

Usage

flightline iap review-screenshot [flags]

iap review-screenshot upload

upload reserves a new IAP review screenshot, PUTs the file in chunks to Apple's CDN, and commits the upload with the local MD5. Idempotent: if a screenshot with the same sourceFileChecksum is already attached to this IAP, returns noop=true without re-uploading. Use --resume to pick up a partial upload from the on-disk checkpoint.

Usage

flightline iap review-screenshot upload <bundleId> [flags]

Examples

flightline iap review-screenshot upload com.example.myapp --product com.example.myapp.lifetime --file ./review/lifetime.png
  flightline iap review-screenshot upload com.example.myapp --product com.example.myapp.lifetime --file ./review/lifetime.png --resume

iap update

update PATCHes the mutable attributes (name, reviewNote, familySharable) on an existing In-App Purchase. Idempotent: if every flag matches the current value, returns noop=true without issuing a PATCH. productId and inAppPurchaseType are immutable post-create: to change either, delete and recreate.

Usage

flightline iap update <bundleId> [flags]

Examples

flightline iap update com.example.myapp --product com.example.myapp.lifetime --name "Lifetime Pro v2"
  flightline iap update com.example.myapp --product com.example.myapp.lifetime --review-note "updated reviewer steps"

lint

lint runs every Flightline preflight rule that does not require live ASC access against the supplied state.yaml. The check covers schema gaps the JSON Schema validator cannot express (yes/no coercion, required-but-empty fields, format: email shape) plus structural rules (localizations completeness, screenshots required-devices). Exit codes: 0 clean (no diagnostics, or info-only) 1 at least one error-severity diagnostic 2 only warnings (no errors) Use --output json for stable LLM/CI consumption; the table form is for humans.

Usage

flightline lint <state.yaml> [flags]

Examples

flightline lint state.yaml
  flightline lint state.yaml --output json | jq '.diagnostics[] | select(.severity=="error")'
  flightline lint state.yaml --output json | jq -r '.summary'

metadata

metadata writes per-locale strings into appStoreVersionLocalizations (description, keywords, whatsNew, promotionalText, marketing/support URLs) and appInfoLocalizations (name, subtitle). Both resources are diff-then-PATCH idempotent: re-running with the same arguments is a no-op.

Usage

flightline metadata [flags]

metadata set

Set per-locale metadata fields (idempotent diff-then-PATCH)

Usage

flightline metadata set <bundleId> [flags]

Examples

flightline metadata set com.example.myapp --version 1.0.1 --locale en-US --name "MyApp" --subtitle "Slogan"
  flightline metadata set com.example.myapp --version 1.0.1 --locale en-US --description "..." --keywords "..."
  flightline metadata set com.example.myapp --version 1.0.1 --locale en-US --whats-new "Bug fixes."
  flightline metadata set com.example.myapp --version 1.0.1 --locale en-US --output json

performance

performance groups read commands over Apple's perfPowerMetrics endpoints: the same battery / memory / hangs / launches / disk-writes metrics the Xcode Organizer "Metrics" tab shows. - app : app-level (cross-build aggregate) - build --build : build-specific metrics Filter by --platform, --category (HANG | LAUNCH | MEMORY | DISK | BATTERY | TERMINATION | ANIMATION | STORAGE), and --device.

Usage

flightline performance [flags]

performance app

Read app-level performance metrics (cross-build aggregate)

Usage

flightline performance app <bundleId> [flags]

Examples

flightline performance app com.example.myapp
  flightline performance app com.example.myapp --category MEMORY
  flightline performance app com.example.myapp --output json | jq '.insights.regressions'

performance build

Read build-specific performance metrics

Usage

flightline performance build <bundleId> [flags]

Examples

flightline performance build com.example.myapp --build 42
	  flightline performance build com.example.myapp --build 2 --version 1.1 --platform IOS
	  flightline performance build com.example.myapp --build 42 --category HANG --output json

performance overview

Read app performance overview

Usage

flightline performance overview <bundleId> [flags]

Examples

flightline performance overview com.example.myapp
  flightline performance overview com.example.myapp --device-type iPhone15,3 --output json

phased-release

Inspect and control phased release for an app update

Usage

flightline phased-release [flags]

phased-release enable

Enable inactive phased release for an eligible update

Usage

flightline phased-release enable <bundleId> [flags]

phased-release get

Show a version's phased-release state

Usage

flightline phased-release get <bundleId> [flags]

phased-release pause

pause an active or paused phased release

Usage

flightline phased-release pause <bundleId> [flags]

phased-release resume

resume an active or paused phased release

Usage

flightline phased-release resume <bundleId> [flags]

plan

Loads <state.yaml>, validates it against the embedded JSON Schema, fetches live ASC state for the same bundleId/version, and prints the change set the apply command would make. Read-only: never writes. Exit code 0 always (diffs aren't errors) unless --exit-on-changes is set, in which case the command returns exit code 2 when changes exist (useful in CI hooks). Examples: flightline plan state.yaml flightline plan state.yaml --output json | jq '.changes | length' flightline plan state.yaml --exit-on-changes

Usage

flightline plan <state.yaml> [flags]

preflight

preflight runs every Flightline rejection-prevention rule against a live App Store version. Live rules query the ASC API for IAP attachment, build state, age-rating completeness, and screenshot device coverage. Offline rules run too when --state-file is provided so authoring mistakes are caught alongside live ones. Without --state-file the live state is fetched and used as the rule input: useful for "is the version actually submittable right now?" checks against any app you have credentials for. With --state-file the user-authored YAML is the input for offline rules and the live ASC state is consulted for live rules. When --state-file is used, its bundleId, version, and platform must match the command coordinates. An omitted state-file platform inherits the command platform (IOS by default); mismatches fail before rules run. Exit codes: 0 clean (no diagnostics, or info-only) 1 at least one error-severity diagnostic 2 only warnings (no errors)

Usage

flightline preflight <bundleId> [flags]

Examples

flightline preflight com.example.myapp --version 1.0.1
  flightline preflight com.example.myapp --version 1.0.1 --state-file state.yaml
  flightline preflight com.example.myapp --version 1.0.1 --output json | jq '.summary'

previews

Manage App Store preview videos

Usage