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

network error #11872

Closed
6 tasks done
almelyar opened this issue Jan 2, 2025 · 2 comments
Closed
6 tasks done

network error #11872

almelyar opened this issue Jan 2, 2025 · 2 comments
Labels
duplicate Issue or discussion is a duplicate of an existing issue or discussion template ignored The user didn't follow the template/instructions (or removed them)

Comments

@almelyar
Copy link

almelyar commented Jan 2, 2025

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

idk

Expected behavior

idk

Actual behavior

idk

Screenshots/Screen recordings

Screenshot_20250102_222054_NewPipe

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=VbZlvXnK0yY
  • Content Country:
  • Content Language: en-
  • App Language: en
  • Service: YouTube
  • Version: 0.27.4
  • OS: Linux samsung/e2sxxx/e2s:14/UP1A.231005.007/S926BXXU5AXK5:user/release-keys 14 - 34
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:230)
	at android.os.Looper.loop(Looper.java:319)
	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.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:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
	at java.lang.Thread.run(Thread.java:1012)


Affected Android/Custom ROM version

android 14

Affected device model

Samsung 24 plus

Additional information

yes

@almelyar almelyar added bug Issue is related to a bug needs triage Issue is not yet ready for PR authors to take up labels Jan 2, 2025
@RyszardGmail
Copy link

I have the same issue. Mine started after 22 december (I couldn't play anything due to this error) from 23 december on version 0.27.1.
I did: uninstalled 0.27.1 and installed newest 0.27.4.
Problem is on my home WiFi so I checked cellular network and on cellular there is no error, everything plays smooth.
My device has Android 12.
Cleared cache, data, position in the app. Cleared app data in android settings.
Installed 0.27.4 on different device also with android 12 and WiFi works on that device. So it is not ban on my IP.
Changed MAC address on phone, changed inner IP address on phone.
Turned off then turned on problematic phone.
I haven't updated any apps recently so it is not case of something which updated itself. Well, updated YT today.
I don't understand why it doesn't work. Maybe YT banned my device as device, by recognizing my device by some unique inner code, some uid number or similar. Not sure.
No more ideas what to do next.

@ShareASmile
Copy link
Collaborator

  • I made sure that there are no existing issues - open or closed - which I could contribute my information to.

"Caused by: com.google.android.exoplayer2.upstream.HttpDataSource$InvalidResponseCodeException: Response code: 403

Duplicate of #11803

Please search (better, with different keywords, particularly take these from first line of the error report/logs OR line after "caused by") so as not to create new issues that have been reported before, especially check from pinned ones, next time when you want to open an issue. Thank you.

@ShareASmile ShareASmile closed this as not planned Won't fix, can't repro, duplicate, stale Jan 3, 2025
@ShareASmile ShareASmile added template ignored The user didn't follow the template/instructions (or removed them) duplicate Issue or discussion is a duplicate of an existing issue or discussion and removed bug Issue is related to a bug needs triage Issue is not yet ready for PR authors to take up labels Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Issue or discussion is a duplicate of an existing issue or discussion template ignored The user didn't follow the template/instructions (or removed them)
Projects
None yet
Development

No branches or pull requests

3 participants