bug(youtube): videos only buffer to 1:10, client-spoofing fails

[suptower]

Type

Error at runtime

Bug description

When watching any video, it will stop loading exactly at the 1:09 / 1:10 mark. The issue seems to be related to client-spoofing.

Additionally, spoofing the version to 16.08.35 seems to resolve the problem, as well as activating Incognito.

Theory was this is the result of A/B testing, however, according to this discord thread, it is not only a certain region impacted.
https://discord.com/channels/952946952348270622/1118066503779098684

Steps to reproduce

1. Have an impacted account.
2. Play any video longer than 70 seconds
3. Try to pass the 1:09 / 1:10 mark. Either by letting the video play or by scrolling (scrolling past this point results in an infinite buffer loop as well)

Relevant log output

NA

Screenshots or videos

Solution

• Spoofing the version to 16.08.35 seems to resolve the problem.
• Activate incognito mode

Additional context

https://discord.com/channels/952946952348270622/1118066503779098684

Spoof App Signature was initially enabled. Tested it with both off and on after the issue has happened, did not alter the outcome.

Acknowledgements

• I have searched the existing issues and this is a new and no duplicate or related to another open issue.
• I have written a short but informative title.
• I filled out all of the requested information in this issue properly.

[oSumAtrIX]

Spoofing the version to 16.08.35 seems to resolve the problem.

Can you try any later versions?

[oSumAtrIX]

This could hint on some client-side checks that can be patched

[suptower]

Spoofing the version to 16.08.35 seems to resolve the problem.

Can you try any later versions?

17.01.35 as well as 17.30.35 do not resolve the buffering problem.

16.08.35 and 16.01.35 do resolve the issue.

[oSumAtrIX]

It may also be that the server reacts differently to the versions. If the server receives one version it does allow playback, if another, it doesn't.

[suptower]

I've also tried it with different versions of YouTube Revanced (18.22.36 and 18.19.35). Currently running 18.22.36 with spoofed 16.08.35, which seems to work for now.

[Julius8900]

May I know how you did try 18.22.36? The client-spoof patch is supported only on version 18.19.35.

[LisoUseInAIKyrios]

If you want to try different spoof targets, you can manually adjust the spoof target by opening the import/export menu and editing the value:

"spoof_app_version_target": "16.01.35"

Change the version to whatever you want, hit import, then restart the app. The "spoof app version target" settings menu will show nothing is selected, but it will be using the custom version you imported.

[suptower]

I've enabled experimental patches support in the settings of Revanced Manager.

I was keen on having the new UI while simultaneously being able to use SponsorBlock, that's why.
Never ran into issues regarding that and I've been using it for over a month or so I think.

[Deathstr0]

Issue might be related to accounts instead of app. Added a old Gmail id that's not been used to watch videos on both YouTube and revanced. That allows me to watch the same video beyond the 1:10 min mark

[Darellku]

Issue might be related to accounts instead of app. Added a old Gmail id that's not been used to watch videos on both YouTube and revanced. That allows me to watch the same video beyond the 1:10 min mark

yes and no, i tried on 2 different account under the same email :
account 1 with revanced 18.19.35 = doesn't work
account 1 normal app/web/revanced 16.08.35 = works
account 2 works on both the latest revanced or normal youtube

[suptower]

It is kinda related to accounts (because incognito mode works in newest versions), but using the regular youtube app, there is no sign of that, since videos play flawlessly there.

[oSumAtrIX]

Turning it off won't fix the issue. Anyways don't spam this issue with "me too" or <i have tried the same and it worked/didnt work> comments

[kitadai31]

Spoofing to 16.42.38 also worked.
16.42.xx or below -> no buffering
16.43.xx or above -> buffering happened at 1:09

To spoof to 16.42.xx, you can use ＠LisoUseInAIKyrios's method above.

[oSumAtrIX]

Fixed with ReVanced/revanced-integrations@be9c948