-
-
Notifications
You must be signed in to change notification settings - Fork 267
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
bug(YouTube - Spoof app version): 17.33.42
spoof target has the same layout as 17.41.37
#2808
Comments
17.33.42
spoof target has the same layout as 17.41.37
Since it's so stubborn to apply the older layout (And the steps above are not explained anywhere else), the spoof version patch could automatically clear the app data when the spoof target is changed. That would fix a lot of issues automatically, including the UI getting stuck on the old library tab layout when spoofing is turned off. The only downside is the YT settings would be reset to default, but the ReVanced settings would be automatically kept. |
Like @LisoUseInAIKyrios already mentioned, the old non-rounded UI is gone for good. I liked it a lot and used it 'till its last day, but it's gone. The difference between the bottom player layouts of 17.33.42 and 17.41.37 are not as big as between the previous and the rounded UI(you can see the difference as shown here:#2776 (comment)) In order to get the 17.33.42 bottom player layout, first you need to spoof to said version and after the restart, force stop ReVanced and clear app cache(that worked for me at least).
Imo, only clearing the cache should do the trick, instead of all data(this has done the trick for me like 90% of the time). Or, clearing cache and clearing data could be added as separate options when spoofing app version. |
Clearing the cache worked for me as well. Edit: after being so stubborn to apply I think automatic clearing the app data might be the most headache free approach, and it's the only surefire way to apply a specific target. The spoof version function is built into YT and baked into the app manifest. So it's expected usage is likely to be for fresh installations and not in environments polluted with app data from different app versions. |
@LisoUseInAIKyrios for me the opposite thing happened. I spoofed to 17.41.37 and the layout changed, but it got stuck on this layout even when I changed back to 17.33.42(even with force stopping and clearing cache multiple times). So yes, if you find a way to clear data when applying this patch and auto keep revanced settings, it'd be a good solution. |
This comment was marked as abuse.
This comment was marked as abuse.
@pep0w while spoofing to 17.08.35, log out of your YT account and try to log back in. You won't be able to. Right now the old versions are being turned off for specific users, and soon it won't work for any accounts. Logging in with those versions is turned off for everyone right now. It makes no sense including those targets if it requires a paragraph of disclaimers and limitations, when soon the targets will be turned off for everyone. |
This comment was marked as abuse.
This comment was marked as abuse.
Because there is a limited set of spoof targets that are useful (and they are already included as options). A free form version text box will have no use after 17.08.x is turned off for everyone. Keep using a fork for the short time you have left, because you probably have only a few weeks left before being cut off. |
This comment was marked as abuse.
This comment was marked as abuse.
The layout structures are sent by the server. Once the servers shut down, the next releases of the clients will remove the deprecated code which essentially would require writing the app from scratch to revert these changes. Unviable. |
Seems the initial issue is invalid. |
Bug description
Installing the patch to fix the watch history has caused the spoofing of app versions to show the new layout instead of what should be the spoofed layout. The spoof only appears to fix the thumbnails of videos on the home screen and nothing else
Error logs
No response
Solution
No response
Additional context
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: