Installing My TV Player on Xbox Series X|S and Xbox One

An Xbox has a browser, a keyboard nobody wants to use, and a controller with two thumbsticks. Every IPTV app that asks you to enter a portal URL on that hardware is asking you to type roughly 60 characters, including a colon, 2 slashes and a port number, with a stick that moves a cursor across an on-screen grid.

My TV Player does not ask. The console's job is to play. The typing happens on a device that has a keyboard.

Getting the app onto the console#

Find My TV Player in the Microsoft Store on the console, under Apps rather than Games, and install it. It runs on Xbox Series X, Series S and Xbox One. No side-loading, no developer mode.

The console build is not the same package as the Windows one. It is a UWP application on modern .NET, for a procedural reason rather than a technical one: the Store on Xbox does not accept WinUI 3 applications, which is what the desktop head is built as. The screens are the same screens, compiled from the same shared XAML into two heads, so what you learn on one transfers to the other.

Signing in without typing anything#

On first launch the console shows a screen with an address, a QR code, and an 8-character code split into 2 groups of 4:

Sign in on your phone

Go to    mytvplayer.app/pair
Then enter the 8-character code

         K7QP - 4M2X

Code expires in 9:42 · We refresh it automatically

Scan the QR with a phone camera, or open the address on any device with a keyboard, and enter the code. While that screen is up the console is not idle. It polls an exchange endpoint, somewhere between every 3 seconds and every 30, asking whether anyone has claimed that code yet. The moment the code is claimed, the console signs itself in. Nothing is typed on the console at any point.

If the start call gets rate-limited, the app waits 45 seconds before asking for a new code. That wait is deliberate: the screen keeps its countdown, the code refreshes on its own, and you do not have to back out and retry.

The flow has 5 possible endings, and only 1 is the good one: signed in, expired, start failed, cancelled, or claimed but not admitted. The last is the one worth understanding, and it gets its own section below.

Once signed in, the console stops at the profile picker. Every time. An earlier startup target assumed the picker would auto-advance. We got this wrong: choosing a profile is a security boundary, not a convenience, so the shortcut was rejected permanently. Kid profiles and PIN gates only mean something if nobody can skip the step.

When the code is right and it still does not work#

There is one failure that looks like a broken code and is not. You enter it, the phone says it worked, and the console tells you the device cannot register right now. The code was fine. What failed is the step after it, for exactly two possible reasons.

The first is the device cap on your plan. Every plan allows a set number of player devices, and a console that would be one over the line does not get a slot. The second is a cooldown: revoke a device recently and that slot is not immediately reusable, which is what stops a revoked slot being cycled endlessly.

Both are fixed in the same place, and neither on the console. Open the web console, look at the device list, remove something you no longer use, and come back. The Xbox will have refreshed its code by then. Browsers never appear in that device list, which sometimes reads as a bug: the web console is a management surface, not a player, so it never takes a slot.

What arrives on its own#

Once paired, your sources, profiles, favorites and guide come down over sync. There is no screen on the Xbox that asks for an M3U URL or an Xtream host. Sources on the console are read-only, showing what was imported and when it last refreshed.

That is a deliberate split. Adding a playlist, editing a source, creating or renaming profiles, and managing devices all happen in the web console or the Windows app. The Xbox watches. Adding an M3U playlist for Xbox and logging in with Xtream Codes for Xbox show it from the other end.

What the first launch actually costs#

A cold first launch on a console was measured at 39.5 seconds and 1.4 GB. That is the worst case in the entire lifecycle: one console, one account, and a catalog being materialised locally for the first time. Later launches do not repeat it, because that work only has to happen once.

It is still the number to know before you decide something is wrong. A console on a loading screen for half a minute on day 1 is doing its job. A console still doing it on day 5 is not, and the place to start is why some channels work on Windows but not on Xbox.

Once you are in, the controller map is worth ten minutes: navigating with the Xbox controller.