-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[YouTube Change] Search result are sometimes empty #1422
Comments
What I said in the issue seems to be true:
If you still notice the issue, please comment here. |
Isn't this related to TeamNewPipe/NewPipeExtractor#415 |
hey its still happening to me on snopyta. |
It's still happening, I don't know why but I didn't have problem for some hours today, then it started again. It's inconsistent, so I'm guessing youtube is testing some stuff. |
can confirm on my instance, very inconsistent also. |
Seems very similar to TeamNewPipe/NewPipe#4201 This was fixed in newpipe. |
Since October 16, the day we updated lsquic.cr and the day we pushed #1412 search results are sometimes empty.
This isn't consistent and doesn't happen every time, but when it does usually a refresh fixes it.
This affect every instance, public or private, with a lot of users or not, with anti-captcha setup or not.
I'm guessing that something about the lsquic.cr update is causing this, but I have really no idea.This is wrong, see the edit bellow.The issue can appear at anytime, even with the same search term sent.
Nothing is displayed in the log.
25 seconds gif of the issue:
Link used: https://invidious.snopyta.org/search?q=test
Edit:
@afuous and @tleydxdy both reported that it was happening for them even without any recent update
@PrestonN (developer of FreeTube) reported that he was also having issue on other project.
It's maybe a new YouTube change, or a YouTube bug (but it seems weird that it's still not fixed on their end though, we'll see next week I guess) that started to happen the day we pushed those change.
Related: TimeForANinja/node-ytsr#71
The text was updated successfully, but these errors were encountered: