Fixed bot detection on all clients #425
Closed
+31
−17
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.
Fixed bot detection on all clients #421
As discovered here #386 (comment) during A/B testing, YouTube now requires
visitorData
to be sent, otherwise a bot detection error is returned.So now pytubefix will retrieve the visitorData and send it in the API request.
This does not resolve bot detection issues when the IP is already blocked.
Changes
inserted visitorData for all clients
Retrieved visitorData from html for poToken clients, and from API response for non-poToken clients (this improves performance)
MWEB
client now requires poToken to obtain functional streamsThis PR also fixes: TypeError: int() argument must be a string, a bytes-like object or a real number, not 'NoneType' #420