Grey text after target/support version bumps

See !109 (merged)

mentioned in merge request !122 (merged)

I tried to fix this by setting android:textColor in styles.xml. Then the text color is not grey anymore but also the disabled entries are white/black and do not look like disabled things anymore.

If we could find out what textColor android resource is being used, we could see exactly where it got changed.

I am assuming this was introduced when bumping targetSdk, not support-v4/appcompat-v7. Will run some tests builds to narrow it down.

Narrowed it down to appcompat-v7. Now let's see exactly what version introduced this bug...

Okay, bumping from appcompat-v7:22.1.1 to appcompat-v7:22.2.0 makes this issue appear.

Sadly, 22.2.1 has this bug too, and 23.0.0 breaks our build without any tweaking.

If the android team tagged their support library releases, I could diff the two versions and find all theme/color/attr changes. Since they don't, it's not going to be as simple.

AOSP really gets on my nerves sometimes. Seriously.

Actually, this happens in all text in F-Droid, except buttons and the action bar.

As a temporary fix, how do you think about going back to appcompat-v7:22.1.1?

You mean 22.1.1? Yeah, I was thinking the same. In the future we want to know whether 23.0.0 or any later version fixes it, to see if it's a bug in appcompat or something we're doing wrong.

If @pserwylo agrees, I'll revert and do the final alpha before a stable.

In fact, 22.2.0 and 22.2.1 only add new features to appcompat: https://developer.android.com/tools/support-library/index.html

So I'm applying this temporary workaround and releasing alpha4. The stable should come shortly after.

Status changed to closed by commit f07497a39cee82cfe6e4f059148ea9b3d0a66c5c

mentioned in merge request !156 (merged)