Video stops 6hrs 16secs in

[ElspethThePict]

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

Open a video of length of more that six hours and let it play from the beginning.

Expected behavior

Video should play as normal until the end.

Actual behavior

At 6 hours and about 16 seconds, the player will stop and produce a network error code. Pressing play on the video will resume it from the place it stopped.

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=ixTb1xoqkvA
• Content Country: GB
• Content Language: en-GB
• App Language: en_GB
• Service: YouTube
• Version: 0.27.0
• OS: Linux Nokia/Sunfire_00EEA/SFI:12/SP1A.210812.016/00WW_1_410:user/release-keys 12 - 31

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:201)
	at android.os.Looper.loop(Looper.java:288)
	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:1137)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
	at java.lang.Thread.run(Thread.java:1012)

---

Affected Android/Custom ROM version

Android 13

Affected device model

Nokia G22

Additional information

No response

[opusforlife2]

This time period is consistent? How many times have you tried?

[ElspethThePict]

The time period is consistent. I've confirmed it twice, and had videos crash out without confirming the time period regularly.

…

On Fri, 31 May 2024, 10:36 opusforlife2, ***@***.***> wrote: This time period is consistent? How many times have you tried? — Reply to this email directly, view it on GitHub <#11102 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASRQE6YEBE6CGGXYYGMBUPDZFBADXAVCNFSM6AAAAABII6TYXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBRGYYTKNJUHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[AudricV]

YouTube streams are only valid for 21540 seconds, so you reached the availability limit by playing them for this duration.

The validity of streams cannot be changed, but the player error handling can (and should) be changed.

[opusforlife2]

There are plenty of 10-hour videos. How does YT deal with those? Does it generate new stream links and seamlessly switch over?

[opusforlife2]

@AudricV Should this be turned into a feature request asking for a link refresh mechanism? Seems like the most straightforward solution.