TeamNewPipe / TeamNewPipe/NewPipeExtractor

Fix video playback by using video ID bound poToken

Open
#1,392 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement YouTube
Dominant language
Java
Stars
2k
Forks
602
Avg merge
3d 6h
Merged PRs (30d)
6

Description

Checklist
  • I am aware that this issue is being opened for the NewPipe Extractor, NOT the app, and my feature request will be dismissed otherwise.
  • I made sure that there are no existing issues - open or closed - which I could contribute my information to.
  • I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
  • This issue contains only one feature request.
  • I have read and understood the contribution guidelines.
Feature description

YT has made a change to support POtoken. This needs to be fixed to prevent http 403 errors in the future. Freetube, Ytdlp and Grayjay have encountered this problem. There is a fix

It seem 403 occurs again due to YT switching to video bound poToken (instead of visitorData bound poToken)
This PR just makes local API use former for all stuff now (the latter is no longer used)

Why do you want this feature?

Fix video playback by using video ID bound poToken. It seem 403 occurs again due to YT switching to video bound poToken (instead of visitorData bound poToken). This PR just makes local API use former for all stuff now (the latter is no longer used)

https://github.com/FreeTubeApp/FreeTube/pull/8137

ytdlp pr; https://github.com/yt-dlp/yt-dlp/pull/14471

Additional information

The application should also be improved accordingly.

NewPipe may not be affected yet because this is an a/b test. Or some other reason. But just in case, just a note

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue provides no file or test names. Start by locating the YouTube POtoken handling and the video playback request path, then compare how video ID-bound and visitorData-bound tokens are selected. Done means playback no longer receives the reported HTTP 403 errors while the existing extractor behavior remains intact.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.