-
-
Notifications
You must be signed in to change notification settings - Fork 335
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) Shorts and Post showing infinity loading in subscription page #2892
Comments
The Shorts selector button shows infinite loading because you have The post selector is showing an infinite loop because you have If you want those items hidden, then do not use those subscription buttons. But if it is not difficult, those buttons should be hidden by the patches just to prevent this situation. |
This is not a bug currently as the patches hide the content. A feature to selectively hide them in the home or search feed could be added |
For anyone who wants to try patching out the selector buttons, they are regular Android layout items (not Litho). So it should be do-able to hide them, just gotta spend the time to figure out an appropriate patch. |
Thank you for your responses. I thought the bug section would be appropriate for this issue, so I opened it under this. I would love to do this patch, but I've got no experience in Android development. But I'll give it a try. |
On YT Hiding the buttons is not difficult, and the work is figuring out how to distinguish what each button is (without relying on simply checking for the language specific strings it shows). |
Cool! Thanks for the detailed explanation, I guess figuring out distinguish button is the tricky part here |
Bug description
I've hidden the shorts and post component in Revanced setting but in subscription page the shorts and post option is visible and clicking on them shows infinity loading screen.
I've attached a video reference below
Revanced.YT.Bug.mp4
Error logs
No response
Solution
No response
Additional context
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: