HomeTechYouTube “Not Supported” bug hits Nvidia Shield TV users

YouTube “Not Supported” bug hits Nvidia Shield TV users

A weird bug has temporarily knocked YouTube and YouTube TV offline for some Nvidia Shield TV owners, triggering an alarming error that tells users the apps “aren’t supported on this device.”

The issue began surfacing on December 11, 2025, with Shield owners reporting that opening either app suddenly threw a “not supported” / “not compatible” message, despite the Shield being a mainstream Android TV streamer. Reports spread quickly across Reddit and NVIDIA’s community forums, and the problem appeared to hit both Shield TV and Shield TV Pro models.

NVIDIA says Google is on it

According to reports citing NVIDIA staff responses on its forums, NVIDIA has already contacted Google and Google is working to resolve the problem. Because NVIDIA’s forum content is largely gated behind JavaScript, the staff statements are best treated as “reported” rather than directly quotable here—but multiple outlets describe the same message from NVIDIA.

Is Google dropping Shield support?

Some affected users said support reps suggested Google had “dropped support” for Shield. There’s no public deprecation notice indicating that’s actually the case, and the way the failure appeared suddenly points more toward a compatibility/certification hiccup or server-side flag gone wrong than an intentional cutoff.

Google’s own YouTube TV documentation lists Android TV as a supported platform (with caveats), but it doesn’t guarantee that every single Android TV device will always be supported under every scenario—especially when bugs like this crop up.

Any workarounds?

There’s no universal fix, but users reported a few temporary options:

  • Reinstalling YouTube / YouTube TV (worked for some)
  • Clearing cache / power-cycling the Shield (mixed results)
  • Casting from a phone as a stopgap (when the native app wouldn’t launch)

Update: signs it’s resolving

Later the same day, users in at least one active thread reported the issue appeared to be resolved, suggesting this may have been a temporary backend problem rather than a permanent support change.

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisment -

Most Popular

POPULAR TAGS

- Advertisment -