Unable to Seek Through Video Timeline

[Sunny-sp]

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.4

Steps to reproduce the bug

1. Open the app.
2. Navigate to the YouTube option.
3. Play any video from the list.
4. Quickly seek the video by interacting with the timeline bar (clicking or dragging) to skip parts of the video.
5. Repeat the seek action 1-2 times back-to-back.

Observe the issue where seeking functionality is not working as expected.

Expected behavior

The video should seamlessly jump to the selected timestamp when the timeline bar is clicked or dragged.

Multiple back-to-back seeking actions should not cause any interruptions, freezes, or errors.

The video playback should resume from the newly selected position without delay or glitches.

Actual behavior

Upon attempting to seek through the video timeline multiple times in quick succession, an error notification appears.

The video playback pauses unexpectedly.

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=SOsP9N8xuuM
• Content Country: IN
• Content Language: en-IN
• App Language: en_IN
• Service: YouTube
• Version: 0.27.4
• OS: Linux Android 13 - 33

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:102)
	at android.os.Looper.loopOnce(Looper.java:211)
	at android.os.Looper.loop(Looper.java:300)
	at android.os.HandlerThread.run(HandlerThread.java:67)
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.ContainerMediaChunk.load(ContainerMediaChunk.java:124)
	at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(Loader.java:412)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
	at java.lang.Thread.run(Thread.java:1012)

---

Affected Android/Custom ROM version

No response

Affected device model

No response

Additional information

No response

[ShareASmile]

See this comment for reason of the closure.
#11852 (comment)