Skip to content
This repository has been archived by the owner on Jan 21, 2024. It is now read-only.

Videos stop playing after a few minutes of playing #351

Open
7 tasks done
CrazyMew37 opened this issue Aug 4, 2023 · 7 comments
Open
7 tasks done

Videos stop playing after a few minutes of playing #351

CrazyMew37 opened this issue Aug 4, 2023 · 7 comments
Labels
bug Something isn't working

Comments

@CrazyMew37
Copy link

Checklist

  • I am able to reproduce the bug with the latest version.
  • I am not able to reproduce the bug with the same version of upstream NewPipe.
  • 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.25.1

Steps to reproduce the bug

  1. Play a video for a bit and it'll crash after some time

Expected behavior

I expect the video to just play in it entirety with no issues

Actual behavior

The videp just stops suddenly and skips to the next one.

Screenshots/Screen recordings

No response

Logs

This happens to me in like every video. What's going on?

Exception

  • User Action: play stream
  • Request: Player error[type=ERROR_CODE_IO_BAD_HTTP_STATUS] occurred while playing https://www.youtube.com/watch?v=AQzITX4DE_s
  • Content Country: US
  • Content Language: en-US
  • App Language: en_US
  • Service: YouTube
  • Version: 0.25.1
  • OS: Linux lge/cv3_lao_com/cv3:8.1.0/OPM1.171019.026/19308143389dd.F:user/release-keys 8.1.0 - 27
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.loop(Looper.java:175)
	at android.os.HandlerThread.run(HandlerThread.java:65)
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:1162)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
	at java.lang.Thread.run(Thread.java:764)


Affected Android/Custom ROM version

No response

Affected device model

LGK30

Additional information

I have battery saver on

@CrazyMew37 CrazyMew37 added the bug Something isn't working label Aug 4, 2023
@OJ7
Copy link

OJ7 commented Aug 4, 2023

latest release should fix this issue (see upstream release notes)

@Kurasami
Copy link

Kurasami commented Aug 4, 2023

Please test the latest version released today (0.25.2) and if it fixes the issue, close this ticket.

@kubo6472
Copy link

It does not
after some time paused in the background, it still fails to play

Exception

  • User Action: play stream
  • Request: Player error[type=ERROR_CODE_IO_BAD_HTTP_STATUS] occurred while playing https://www.youtube.com/watch?v=EwgZaSYuBLc
  • Content Country: US
  • Content Language: en-US
  • App Language: en_US
  • Service: YouTube
  • Version: 0.25.2
  • 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: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)


@Atemu
Copy link

Atemu commented Aug 19, 2023

I don't think this is the place to discuss this. This is clearly an upstream issue. Please reproduce the issue using regular NewPipe and contribute your findings upstream where/if appropriate.

@825i
Copy link

825i commented Aug 19, 2023

It's definitely fixed in the latest version. I think he's still not updated or hasn't cleared cache but yes it is an upstream issue. Should be reported there, not here.

@kubo6472
Copy link

It's definitely fixed in the latest version. I think he's still not updated or hasn't cleared cache but yes it is an upstream issue. Should be reported there, not here.

Do you see "Version" in my buy report? If you're referring to me, I'm definitely updated 😉

@825i
Copy link

825i commented Aug 19, 2023

It's still not a problem with this app. It's an upstream issue so you're wasting your time here. We don't fix or work on upstream issues. You should report it there.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants