Play's "no countries" error described the empty alpha track the pipeline was aimed at

Google's message was accurate. It reported the state of the track the pipeline asked about, and the pipeline was asking about `alpha` ^[7]. The countries the team kept re-checking in Play Console belonged to a different track: a custom-named one they had created themselves, holding the live release with real testers and real country availability ^[6]. Three theories went past that. The last one was closed off by a documented limit, according to the dev.to write-up: a track's country availability is not writable through Google's own API for anything other than the production track ^[5].

Asking Play for every track the staff app had returned five ^[6]. Four of them, the standard `production`, `beta`, `alpha` and `internal` names, were empty and had never been used ^[6][1]. One shared "publish to this track" value therefore had four ways to be wrong and one to be right. The student app's active track happened to be named `alpha` literally, which is the only reason half the releases worked ^[8]. The reported fix is one track variable per app ^[9].

The second defect is a parse failure in the workflow file. The first attempt at per-app result reporting put an Actions expression inside a shell assignment: `result="${{ failure() && 'failure' || 'success' }}"` in a `run:` block ^[10]. `success()`, `failure()`, `cancelled()` and `always()` are only valid inside an `if:` condition, and using them anywhere else, including inside `run:` wrapped in `${{ }}`, makes the entire workflow file invalid ^[13]. The run came back with zero jobs, and its name fell back to the literal file path instead of the workflow's name, which the write-up identifies as GitHub's signature for a file it could not parse ^[11].

A YAML gate in pre-commit does not catch this. `yaml.safe_load()` in Python, or any plain YAML linter, reports the file as completely fine, because as YAML it is ^[12]. The file is well-formed and the expression is in the wrong place, and only the Actions parser knows the difference.

The structural call the team made was that "code is production-ready" and "ship this specific app to the Play Store" had to be two separate decisions, not one automatic consequence of the other ^[15]. The concrete change described in the post is the per-app track variable ^[9]; the write-up states the decision without publishing the gate that implements it, and genericizes the track name and version code ^[6].

For the track failure to transfer to your pipeline, one of two things has to be true: your live testing track was created under a name of your own rather than one of Google's four, or a single config value feeds more than one app. Both were true here ^[6][7]. The YAML failure transfers more widely, because it only requires that someone move an expression function out of an `if:` and into a `run:` ^[13]. This is part 2 of a five-part series; parts 3 and 4 cover an Actions storage-quota crisis ^[1][14].