Separate the selected channel from the installed application
IPTVnator’s desktop update guide says that choosing Stable changes future update checks. An installed nightly remains until a newer stable release is available. Selecting a channel is therefore a different action from replacing the executable that is already running.
Open About and record both the selected channel and the installed version or build. These two values can legitimately describe different things. For example, a computer may follow Stable for its next update while still running the nightly it installed during a previous investigation.
Check whether the new channel choice was saved
The documented control is Settings, About, Update channel. Save the intended selection and read the channel attached to the check result. The developer also notes that an already downloaded or ready update retains its earlier channel identity; changing a selector does not silently replace that artifact.
Keep a short sequence of the displayed state: installed build, selected channel, saved choice and offered update. This makes the result easier to assess than repeatedly pressing Check while changing the selector. If a pending update belongs to the previous channel, read that state before deciding the next action.
Treat a data migration as separate from an executable
The developer explains the forward-only behavior in terms of newer database changes that an older stable application may not understand. Do not assume that installing an older binary reverses the profile’s migration. The same desktop profile is used; selecting Nightly did not create an isolated test library.
Before participating in a future nightly test, export the supported source state and identify anything that backup does not contain. For a critical viewing computer, decide whether the specific fix is worth a development build. A feature being available on a development branch is not proof that the previous stable profile can consume its resulting data.
Report the failed update stage
If the expected forward update is absent or fails, name the installation format as well as the operating system. A Linux AppImage and a package-manager installation can have different update routes. Follow the action the application actually offers for that format.
Include the exact build or commit when describing a nightly regression, with the source type, engine and shortest reproduction. The desired result is a clear update path and preserved profile evidence. It is not a claim that selecting Stable can undo every change from a nightly session.
Questions answered
Why does About still show the nightly build after I chose Stable?
The documented updater waits for a newer stable release. The choice controls future checks and does not downgrade the installed app.
Does switching update channels make a separate test profile?
No. The developer says a nightly uses the app’s existing data. Plan recoverable source state before testing.
Is “Linux” enough detail for an update issue?
Include the package format. AppImage, distribution packages and package-manager installations can use different update actions.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.