-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
[FIXED] [YouTube side issue which affected official clients too] Mandatory reCAPTCHA challenge opens an HTTP 405 error page #8183
Comments
This comment was marked as duplicate.
This comment was marked as duplicate.
On my device NewPipe crashes with an UI error. Already posted this on another issue report (that was made 2 minutes before this one yet was the only one showing up for me) but for completion sake I will put it here as well. Unsureif unrelated issue though. Exception
Crash log
|
For everyone: please test the APK of TeamNewPipe/NewPipeExtractor#780 and let me know if you can reproduce the issue. Thanks! |
This build solves is for me! Don't even have to enter a reCAPTCHA, video just plays. |
This comment was marked as duplicate.
This comment was marked as duplicate.
@TiA4f8R
reCAPTCHA requirement is gone, didn't even have to solve it. Thank you for your work! |
The issue has been solved by YouTube, so I am closing this issue. |
MOD EDIT: The issue was from YouTube's side and has been fixed, see https://support.google.com/youtube/thread/159624032/known-issue-4-12-2022-issues-across-youtube-services
Checklist
Affected version
0.22.1
Steps to reproduce the bug
Expected behavior
I am redirect to some kind of reCAPTCHA page that where I can solve a reCAPTCHA and press Done.
Actual behavior
I am redirected to a page with an HTTP error 405.
The page reads:
Screenshots/Screen recordings
Logs
No response
Affected Android/Custom ROM version
Android 11
Affected device model
Google Pixel 4a
Additional information
Two other users on IRC and one friend of mine also have the issue.
For all the users, NewPipe worked fine yesterday. It is highly likely that something broke after a change from Google, since yesterday.
The text was updated successfully, but these errors were encountered: