-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(YouTube/Spoof client): partial fix for watch history issue of brand accounts on iOS clients #2297
Comments
Will this work when spoofed to this version or earlier (via the spoof app version patch)? |
This fix doesn't work with It seems to be related to the YouTube API response changing in YouTube versions after 18.38.45 |
What is the goal of this issue tracking? Improve the already existing patch by ReVanced? |
ReVanced doesn't fix brand account's watch history issues See #2290 (comment) and #2290 (comment) |
…nd accounts on iOS clients inotia00/ReVanced_Extended#2297
…nd accounts on iOS clients inotia00/ReVanced_Extended#2297
Then the title of ReVanced's PR is wrong. 🤔 |
reflected in revanced-patches-4.12.1 |
Application
YouTube
Feature description
This is not a patch request, but a description of the feature that will be introduce in the next release.
Watch history does not work on brand accounts when spoofing with iOS clients.
I've been tracking this known issue for a long time and found out that SmartTubeNext can force the generation of Watch history.
(This is invoked by the TrackingService class in the MediaServiceCore library.)
Of course, it is impossible to directly apply the method of SmartTubeNext, which is a completely different client, to ReVanced, but it seems possible to apply it to ReVanced with restrictions.
If this is implemented in ReVanced, there are the following limitations:
Motivation
Although there are many prerequisites, it may be useful for someone.
Acknowledgements
The text was updated successfully, but these errors were encountered: