YouTube fixes sign-in failures on TVs and consoles
Google says an issue that locked people out of the YouTube app on televisions and games consoles, even with the correct password, is now fully fixed.

YouTube says it has fixed a sign-in fault that affected its app on televisions and games consoles. In a community post headed “[Fixed] Issues logging into YouTube on TVs and gaming consoles”, the company acknowledged reports from people who could not log in on what it calls living room devices.
The failure was more than an inconvenience for anyone already signed in. Users reported being logged out and then unable to get back in, with correct passwords failing to take. YouTube says its teams investigated the reports and confirmed the issue is “now fully fixed”, and that users should no longer run into problems signing in.
What to do if you were locked out
YouTube’s guidance is simply to try signing in again on the affected device. The notice was published in the company’s help community, where it posts updates on known and resolved issues affecting the platform.
Why a sign-in bug is worse on a television
Televisions and consoles are the awkward corner of any account system. There is usually no keyboard, no password manager and no easy fallback to a browser, so a login that fails leaves the app stranded rather than degraded. That makes the living room the place where sign-in reliability matters most and where a fault is least recoverable without a second device to hand.
Our opinion
The quiet part of a story like this is how much of television now depends on a session token holding. YouTube is treated as furniture in living rooms, bundled into the firmware of most smart TVs and onto every console dashboard, and it earns that position by working without anyone thinking about it. When sign-in breaks, the failure is not subtle: the app sits there asking for a password that is already correct. Google fixed this one within days, which is the right speed for a bug that turns a paid service into a dead screen, but shipping signed-in state that survives an app update would be a better use of engineering than apologising for it afterwards.