-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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]: sorting is messed up #4077
Comments
+1 same issue here |
Can confirm this is broken in last 2 builds. This is specific to Alphabetical. Work around right now is to change your sorting to Alphabetical (fast previews) until this is fixed. Settings > User Interface > Channels Section Sorting |
Same problem here. And some content still isn't showing in channel view unless you explicitly "open channel". We seem to keep going backwards to old, resolved problems. |
Yeah, sorting of channels is messed up now. Also after exiting a video of a channel in the red new content section the channel is now not red and sorted with the rest. I have to leave channels and come back to see the rest or scroll all the way back. |
I am facing the same issue on both stable and beta, I haven't updated my stable version in months because it just worked without issues, I was using the beta version today and noticed this issue, So I thought I would use the stable version with out the issue, Nope the issue is present in the stable version as well. Which makes me believe it's on YT's side or something they've changed. |
Duplicate #4070 |
Checklist
Affected version
24.53
Device Type
Smart TV/Box
Affected Android
Android TV 11
Steps to reproduce the bug
Go to channel list
Actual behavior
Until now, channels with new content were coloured red and in alphabetical order and the other channels were below that in alphabetical order. Now there is just the separation between channels with or without new content. No alphabetical order within.
I changed nothing before or after the update to my settings.
Additional information
The text was updated successfully, but these errors were encountered: