[BUG]: Channel new content highlight won't go away after visiting

[r00tnpm]

Checklist

• I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.

Affected version

31.30 Stable

Device Type

Smart TV/Box

Affected Android

Android TV

Steps to reproduce the bug

1. Assume settings > channel sort type = new content first
2. Go to "Channels" on left panel
3. Channels with new content will be sorted on top, with red highlight of channel name box
4. Click on new content
5. Back up to "Home" screen on left panel
6. Go back to "Channels" on left panel - the same channels are still highlighted in red

Actual behavior

Noticed this new bug today, after upgrading to 31.30 Stable, in the past after browsing channels with new content, then back out, the next time I visit channel section, the red highlight would go away, so all channels would be sorted normally, but this feature appears broken.

By the way, I noticed now that the space between square box of each channel is much wider in 31.30, it looks weird, could we pls switch back to the old ways?

Thanks!!

Additional information

No response

[gcogger]

Same for me on 31.37 beta. I now have a significant number of channels permanently showing in red, so I can no longer see which channels have new content. Wish I hadn't updated this time.

[Vitriolic-One]

Having the same problem

[Tidone]

Can confirm, however this bug has nothing to do with an app update.
I've been running 31.30 stable and 31.37 beta on my devices for a few days, and the bug only started happening about a day ago.

It seems Youtube changed something on their API.

[u84six]

Same for me on Fire Stick

[gcogger]

Can confirm, however this bug has nothing to do with an app update. I've been running 31.30 stable and 31.37 beta on my devices for a few days, and the bug only started happening about a day ago.

It seems Youtube changed something on their API.

For me the issue occured immediately on updating to 31.37, so I assumed it was because of the new version. From what you say, it sounds like that was just a coincidence.

[MrRobot12]

Came here to report this same bug.