YouTube Error Code 152-18 | How to Fix

Error code 152-18 is almost exclusively associated with SmartTube (an unofficial YouTube client for Android TV/Firestick) or similar third-party “wrapper” apps like Piped.

It usually indicates a failure to fetch the video stream, often triggered by YouTube’s recent security updates or age-restriction filters.

As of March 2026, here are the confirmed fixes:

## 1. Update the App (Most Likely Fix)

YouTube frequently changes its internal “playability” logic, which breaks older versions of third-party apps.

  • SmartTube Users: Check for a “Beta” or “Stable” update in Settings > About > Check for Updates.

  • If the in-app update fails, you may need to manually download the latest .apk from the official GitHub (yuliskov/SmartTube) because version 30.x and older have been reported to get stuck on this error.

## 2. Change DNS Settings (Network Conflict)

This error often occurs when the app’s player can’t resolve YouTube’s video servers via your current internet provider’s DNS.

  1. Open SmartTube.

  2. Go to Settings > Player > Developer Options.

  3. Check the box for “Prefer IPv4 DNS” or “Prefer Google DNS”.

  4. Force Stop the app and restart it.

Also Read : Baba Ijebu Result for Today Prediction

## 3. Reset App Data & Re-Login

Sometimes the error is tied to a corrupted session or an “age-restricted” flag on your account that the app can’t bypass.

  • Clear Cache: Go to your TV/Firestick’s Settings > Apps > SmartTube > Clear Cache (and Clear Data if cache doesn’t work).

  • Switch Accounts: Some users have fixed this by logging out and logging back in, or using a different “dummy” Google account.

## 4. Age Restriction Issues

If you are seeing this code on a specific video but not others:

  • The code 152-18 is a known “Content Not Available” exception for age-restricted content.

  • Ensure the account logged into the app has a verified age over 18. If you are not logged in, these videos will consistently throw this error.


## Summary Checklist

Step

Action

Why?

1Update to Version 31.03 or higherFixes broken internal search logic.
2Enable Prefer IPv4Bypasses DNS resolution errors on some ISPs.
3Clear Storage/DataResets corrupted login tokens.

Be the first to comment

Leave a Reply