-
-
Notifications
You must be signed in to change notification settings - Fork 448
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 #6982
Comments
Tracked at TeamNewPipe/NewPipe#11934 |
Yo bro, i'm also facing this problem for couple of days now. I hope you guys fix this problem soon. |
There's a PR open for this, already: TeamNewPipe/NewPipeExtractor#1262 |
Why the devs are not implimenting this? |
@jellyfish404 to keep the app bug-free and avoid redoing the whole thing, it's better to wait for the PR to mature before beginning the implementation. We are on the fastest course of action for a fix, don't worry. |
PR merged. |
Updated in #6995. Nevertheless it'll take some days until I can create an update, the current nightly version has seen a lot of changes and thus isn't stable enough for a release yet, as most critical bugs should be fixed before considering a new release. |
Are there any workarounds I can do to fix it in the meantime? I have the same error: "IOS player response is not valid". I can also wait. |
Not really, I expect to get everything ready for a release this weekend. |
Great |
Thanks for fixing this. I updated to 0.27.0 and is actually working now. |
"IOS player response is not valid" came again 😞 |
Just now got this, watched a video fine then boom invalid responses again |
It's known upstream: It might be beneficial subscribing to that issue to track a potential fix, since it has to be fixed upstream. iF there is a fix there, it is waiting till the maintainer of this project has time to implement it here. |
Sadly, it happens again. That same error, some videos work. |
Yep I got the same error |
Yeah, hopefully it will be fixed soon. |
As a general note, please refrain from adding "me too" comments until you have additional info to provide. Neither here nor anywhere else. These comments aren't helpful, cause unnecessary noise and rather impede both devs and other users from finding the comments that provide useful info. Thanks everyone 👍 As a service note, TodorovicSrdjan found a temporary workaround in TeamNewPipe/NewPipe#11980 (comment) that worked for me repeatedly too: Use the Share feature to open the YouTube video in your browser and reload the page a few times (the number of reloads required varies). Sometimes this causes YouTube to unblock your IP address temporarily and LibreTube will be able to load the video using the local streams extractor. No guarantees given though, it's just a temporary workaround, the number of reloads required varies greatly and might not work at all for you. And, by the way: There's no need to report whether this workaround works for you too or not. |
If you bug the absolute living of the youtube api it eventually goes trough Which is a bit annoying but its the only workaround i've found |
Steps to reproduce
Expected behavior
The video will play every time.
Actual behavior
Most of the time the video will not play at all and will pop up that error.
LibreTube version
0.26.0
Android version
14
Other details
Searching for this the only issue that came up is #5855, which doesn't seem related, but I will note that I tried the fix from there of forcing HLS, and it did not address the issue.
I also have piped proxy disabled. Trying via VPN does not reduce the frequency of the error.
Acknowledgements
The text was updated successfully, but these errors were encountered: