[YouTube] Videos made for kids are only available in 360p

[Videogamer555]

Checklist

• I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
• I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.
• I have read and understood the AI policy. The content of this bug report is not generated by AI.

Affected version

0.29.0

Steps to reproduce the bug

Go to https://www.youtube.com/watch?v=DLxCHtoi518 in NewPipe and notice that 360p is the only playback or download video resolution.

Expected behavior

It should have multiple playback resolutions. For the particular video I am using as an example in this bug report, that should include resolutions up to 720p.

Actual behavior

The only resolution it shows for either immediate playback or for download, is 360p.

Screenshots/Screen recordings

No response

Logs

No response

Affected Android/Custom ROM version

No response

Affected device model

No response

Additional information

This is a bug that previously was fixed, when NewPipe added the needed features to interface with YouTube's new and more advanced internal playback API. But the bug is back, indicating that once again YouTube must have changed the exact implementation of this API. Please fix this bug again by patching NewPipe with the latest YouTube internal API. I'm surprised that nobody else has mentioned that this bug is back.

[AudricV]

It is a video made for kids, so that's an expected behavior. See https://github.com/TeamNewPipe/NewPipe/releases/tag/v0.28.8.

You will not be able to get a higher quality until we add support for YouTube custom playback protocol, SABR.

[Videogamer555]

How does YouTube treat videos for kids separately, such that the playback is handled differently? Didn't YouTube already add the new protocol for all videos? And I thought your workaround you already used worked by adding support for the new protocol.

[shishcraft5]

it's a workaround, new SABR protocol just isn't there at all, newpipe still uses android_vr extraction endpoint