feat(YouTube - Spoof client): Re-add TestSuite as a spoofing option

theblackhole commented 2 months ago

Feature description

For the YouTube Client Spoof patch, re-add Android TestSuite as a spoofing option in addition to current options (Android VR and iOS)

Motivation

I've been using a branded account as my primary account for years and there are some significant issues with the current spoofing choices offered (also described in #3208):

either, with the choice of iOS spoof set by default, the viewing history no longer works: we then fall quickly into a cycle where YouTube only recommends videos that have already been viewed (it's quite frustrating)
either, with the choice of Android VR spoof, the paused or finished video automatically restarts after few seconds, when you change applications, lock the smartphone, etc... (as described by @MelvynEzi , it's always, not random)

Previous versions with Android TestSuite (before #3230) worked fine for me. If there were limitations, I didn't notice them (for my daily use anyway, it's probably different for other people)

Acknowledgements

[X] I have checked all open and closed feature requests and this is not a duplicate
[X] I have chosen an appropriate title.
[X] All requested information has been provided properly.

Jeanfeels commented 1 month ago

I am also experiencing this issue and would like to add a couple of extra reasons to implement it:

My non-brand youtube account is attached to my irl name, and as such i have never used it from privacy concerns. I feel like being forced to use it if i want to have a smooth experience on Youtube is a privacy risk which makes me feel unsafe.
All my history and subscriptions are tied to my brand account, and migrating them across is very inconvenient.
I am a hobbyist youtube creator and as such I need to be primarily focused on my brand account. Switching back and forth is not a good solution.

Please consider these additional reasons when looking into this feature request.

LisoUseInAIKyrios commented 2 weeks ago

This issue will be obsolete when https://github.com/ReVanced/revanced-patches/pull/3582 is merged, as all known bugs are fixed by that PR

ReVanced / revanced-patches