[YouTube] Workaround 403 HTTP errors of ANDROID client streams #960
+541
−456
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…se codes Using the player parameters used to get stories seems to fix the issue, which affects currently only certain countries such as UK. This is a workaround and should be fixed in a better way (by changing the InnerTube additional client used for videos or finding what is now required in Android player requests).
FireMasterK
approved these changes
Oct 30, 2022
This was referenced Nov 4, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR tries to workaround the new detection of third-party clients by YouTube with the
ANDROIDInnerTube client, returning HTTP 403 errors for stream URLs got from it, by using player parameters of stories. This behavior is currently A/B tested in some countries (like the video replacement when not providing required payload parameters and user-agent) (with around a 15% reproducible rate), such as UK.This issue needs to be investigated in the near future and affects other third-party clients which make use of this InnerTube client.
Fixes TeamNewPipe/NewPipe#9038.