Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Player error #12047

Open
6 tasks done
Da-Cavolo opened this issue Feb 17, 2025 · 0 comments
Open
6 tasks done

Player error #12047

Da-Cavolo opened this issue Feb 17, 2025 · 0 comments
Labels
bug Issue is related to a bug needs triage Issue is not yet ready for PR authors to take up

Comments

@Da-Cavolo
Copy link

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

Steps to reproduce the bug

  1. Tap on any video
  2. Watch it

Expected behavior

The video should keep playing until the end.

Actual behavior

The video randomly stops playing and a notification shows up saying "NewPipe encountered an error, tap to report". Upon closing and re-opening the video, it stops again at the same timestamp with the same notification. This has happend for multiple videos and it seems to happen more frequently when queueing videos. Closing and re-opening the app each time it happens "fixes" the issue.

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=DVysyBRfVX4
  • Content Country: GB
  • Content Language: en-GB
  • App Language: en_GB
  • Service: YouTube
  • Timestamp: 2025-02-17T07:26:22.229+01:00
  • Package: org.schabi.newpipe
  • Service: YouTube
  • Version: 0.27.6
  • OS: Linux samsung/a13nseea/a13:13/TP1A.220624.014/A135FXXU4CWE5:user/release-keys 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:226)
	at android.os.Looper.loop(Looper.java:313)
	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:425)
	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

Samsung Galaxy A13

Additional information

• The affected device is rooted
• This same bug has been affecting the app for many versions, not just the most recent one

@Da-Cavolo Da-Cavolo added bug Issue is related to a bug needs triage Issue is not yet ready for PR authors to take up labels Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue is related to a bug needs triage Issue is not yet ready for PR authors to take up
Projects
None yet
Development

No branches or pull requests

1 participant