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

IOS player response is not valid error when loading some videos #3954

Open
1 task
jamesdrake101 opened this issue Jan 20, 2025 · 4 comments
Open
1 task

IOS player response is not valid error when loading some videos #3954

jamesdrake101 opened this issue Jan 20, 2025 · 4 comments
Labels
bug Something isn't working

Comments

@jamesdrake101
Copy link

jamesdrake101 commented Jan 20, 2025

Official Instance

Describe the bug

Just making sure this problem is tracked here and the upstream fix is applied. Piped is completely broken for me at the moment, due to this issue.

Thanks.

To Reproduce

Play any video

Expected behavior

The video plays

Logs/Errors

IOS player response is not valid

Browser, and OS with Version.

Any client

Additional context

Upstream issue: TeamNewPipe/NewPipe#11934

@jamesdrake101 jamesdrake101 added the bug Something isn't working label Jan 20, 2025
@Atemu
Copy link

Atemu commented Jan 21, 2025

https://github.com/TeamNewPipe/NewPipeExtractor/releases/tag/v0.24.4 has been released with the fix; just needs to be applied.

@jamesdrake101
Copy link
Author

@FireMasterK @Bnyro If you can use any assistance (for menial work, manual testing etc) to fast track applying this fix, please ask. At the moment I need to reload 90% of the videos I watch at least 5-6 times before they start.

@Atemu
Copy link

Atemu commented Jan 21, 2025

I pushed this to my fork I just made for testing and it works in my deployment.

Atemu/Piped-Backend@bb7eada

I can't PR this obviously because it points to my NPE fork where I simply merged the upstream tag:

Atemu/Piped-Backend@bb7eada

@Atemu
Copy link

Atemu commented Jan 21, 2025

(The whole process around updating this dependency sucks tbh. Jitpack is a crutch and, while it does its stated job, that just doesn't really work well because you must always push to GH. I don't know a better solution though unfortunately short of vendoring the entire tree via e.g. git subtree.)

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

No branches or pull requests

2 participants