Publishing a live TV app to Google Play starts with a build Google will accept, and that part is done: the panel compiles the channel's Android player and signs the App bundle with your upload key, so there is no Android Studio and no keystore of your own. The rest is console work in your own developer account - the store listing, the App content declarations, the foreground service, and, on a personal account opened after 13 November 2023, at least two weeks for the mandatory closed test.
Menu names follow Play Console as of 2026. Where Google relabels a page, its purpose stays the same; match on that.
Ownership: the listing belongs to whoever owns this developer account. The panel never publishes on your behalf, and app transfers between accounts are possible but slow, so register under the long-term owner.
Production access on personal accounts created after 13 November 2023 is gated on a closed test with 12 or more opted-in testers for 14 consecutive days. Organization accounts skip it.
Main store listing, in the Store presence section:
Each is linked from the Dashboard's setup checklist and must be answered before the first release.
Back up the upload key with Download upload key on the panel's Android upload key card: a .p12 whose password is displayed once. Every later .aab is signed with the same key.
While the channel is off air the app shows its "We'll be live soon" slate and polls until the stream returns, then plays without user action. Correct for viewers, but a reviewer who sees only the slate can conclude the app is broken.
Updates: stream URL, description, logo, links and contact details are read from the channel's live feed and never need a release. Name and icon changes do: rebuild (the version code increments) and release the new .aab.
Who the closed test applies to, what Google asks about the foreground service, and what the app has to show a reviewer.