[YouTube] HTTP error 403 around 1 minute mark

[opranda]

Please also see About YouTube playback errors - YouTube changed some things to get working streams

---

Checklist

• I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
• I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected version

0.27.0

Steps to reproduce the bug

When I click play, the video loads and the message "Network error" appears and nothing happens

Expected behavior

No response

Actual behavior

No response

Screenshots/Screen recordings

No response

Logs

Exception

• User Action: play stream
• Request: Player error[type=ERROR_CODE_IO_BAD_HTTP_STATUS] occurred while playing https://www.youtube.com/watch?v=GnUCGS0KRqM
• Content Country: RU
• Content Language: ru-RU
• App Language: ru_RU
• Service: YouTube
• Version: 0.27.0
• OS: Linux Android 5.1 - 22

Crash log

com.google.android.exoplayer2.ExoPlaybackException: Source error
at com.google.android.exoplayer2.ExoPlayerImplInternal.handleIoException(ExoPlayerImplInternal.java:644)
at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:616)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:194)
at android.os.HandlerThread.run(HandlerThread.java:61)
Caused by: com.google.android.exoplayer2.upstream.HttpDataSource$InvalidResponseCodeException: Response code: 403
at org.schabi.newpipe.player.datasource.YoutubeHttpDataSource.open(YoutubeHttpDataSource.java:422)
at com.google.android.exoplayer2.upstream.DefaultDataSource.open(DefaultDataSource.java:263)
at com.google.android.exoplayer2.upstream.TeeDataSource.open(TeeDataSource.java:52)
at com.google.android.exoplayer2.upstream.cache.CacheDataSource.openNextSource(CacheDataSource.java:796)
at com.google.android.exoplayer2.upstream.cache.CacheDataSource.open(CacheDataSource.java:609)
at com.google.android.exoplayer2.upstream.StatsDataSource.open(StatsDataSource.java:84)
at com.google.android.exoplayer2.source.chunk.InitializationChunk.load(InitializationChunk.java:99)
at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(Loader.java:412)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)

---

Affected Android/Custom ROM version

No response

Affected device model

No response

Additional information

No response

[nash268]

for me when error occurs it's always at 00:59 time stamp.

[krushia]

Confirming that:

1. The first part of a video will play before the error occurs
2. After the error, the triggering video will no longer play at all
3. After the first occurance, there appears to be an increased probability of triggering the error with other videos (but they may still play okay)
4. Restarting NewPipe usually fixes it
5. It happens sporadically

[juanfra684]

Clearing the metadata in the settings menu fixed the problem for me. I didn't change the DNS or anything this time.

[acarasimon96]

YouTube Music uploads (the ones that are just album art rather than an actual video) don't seem to trigger it either, maybe they use a different format that doesn't have the same problems?

In my experience, both normal and YouTube Music videos are affected; I get the same exact behavior on either kind.

[ale5000-git]

I wonder if this fix may apply also to NewPipe: yt-dlp/yt-dlp#10456

[opusforlife2]

The bug is known. There's no need to add 'me too' comments. Locking temporarily.