flitz tracks
List an app's tracks, each with its newest build and its track link; --app, --limit, and --json.
flitz tracks lists one app's tracks and the link that always opens each
track's newest build. A track is usually a Git branch — see
Apps and tracks.
flitz tracks # the current project's app
flitz tracks --app acme_appfeature-login feature/login 2026-09-28 14:02 1.4.0+12 https://…/acme_app/feature-login
main 2026-09-27 17:45 1.4.0+11 https://…/acme_app/main
5e0c2a9b71d4 Unassigned no publish yet https://…/acme_app/5e0c2a9b71d4One line per track, the one with the newest build first: the track key, its
name when it differs from the key, when its newest complete build started and
its version (or no publish yet), and the track link. The link always opens
the newest complete build, so it is the one to share. Unassigned holds the
publishes made without a branch.
Flags
tracks accepts the global options, including
--json, plus these:
| Flag | Default | Purpose |
|---|---|---|
--app <key> | app: in flitz.yaml, else the pubspec name | The app whose tracks to list. |
--limit <n> | 20 | How many to list, from 1 to 200. |
An app with no tracks prints No tracks yet. on stderr.
--json
--json prints { "fallbackTrackKey": "…", "tracks": [ … ] }.
fallbackTrackKey is the key of the app's Unassigned track. Each track
carries key, name, trackUrl, and latest — its newest complete build,
shaped like a publishes --json entry — when it has
one.
Errors
| You see | Code | Meaning |
|---|---|---|
no app named → pass --app <key> | 1 | No --app, and the current directory has neither app: in flitz.yaml nor a pubspec.yaml name: to take the app from. |
app <key> does not exist → run flitz apps list | 1 | The key names no live or archived app. |
tracks works for any member of the organization and for a CI job with
FLITZ_APIKEY. It needs an active organization license; while
it is inactive it fails with exit 3.