Font colors don't match theme

[Mr-Kanister]

Checklist

• I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
• 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.
• I have read and understood the contribution guidelines.

Affected version

0.27.6

Steps to reproduce the bug

1. Have the dark theme enabled
2. Open any video (doesn't work always, mostly after a fresh start of the app)
3. Wait for it to be loaded
4. See the comment's and every other video preview's fonts to be black on black background
5. When changing phone orientation, it switches back to normal

Expected behavior

The font color should always stay white

Actual behavior

The font color changes from white to black

Screenshots/Screen recordings

screen-20250416-211622.webm

Normal:

After loading the video:

Logs

No response

Affected Android/Custom ROM version

Android 15 / Graphene OS build 2025041100

Affected device model

Google Pixel 7

Additional information

This bug appeared a long time ago, I just was too lazy to report it. I can't do anything about it, I tried reinstalling, I tried the beta and nightly releases.

The video shows the app after a clean start, everything looks normal. I then open a video and wait for it to load. You can then see that the comment's font is black instead of white. You can still kind of read them by tapping on them. Switching back to the other screens, they now also changed their font to black. After changing the phone's rotation, it all goes back to normal.

Unfortunately this bug seems to not affect many people as it wasn't reported yet to my knowledge. Also it doesn't happen on every video start as you see in the second try in the video.

If you have something else which I can debug to help you, I'd be happy to help.

[ShareASmile]

• I made sure that there are no existing issues - open or closed - which I could contribute my information to.

The issue you are reporting is actually a duplicate of an Issue already reported #12016 and already fixed on dev branch by merge of PR #12035.

Can you confirm by retesting nightly build?

Although, please always check for duplicates (from open & closed ones)
before opening a new issue and to avoid a duplicate, search (with better keyword/s) next time you want to open an issue, thank you.

[Mr-Kanister]

Oh, I'm sorry, I thought I searched thoroughly enough for duplicates. I will recheck the nightly build and close this issue if the bug doesn't appear there.

[Mr-Kanister]

Already fixed.