#Android studio theme color apk#
#Android studio theme color code#

This happened to be used for colorPrimary. This resulted in a null value for saGreen. First there was an invalid colour value which somehow did not cause AAPT to barf. ConclusionĪ perfect combination of factors produced this issue. But it’s still something of a mystery why this value did not produce an error from AAPT. This now explains why the AppCompat theme check was failing – because there was not valid value for colorPrimary.

#Android studio theme color apk#

I checked the resource definitions that were added to the APK and found that saGreen was defined with an empty value. īut, for some reason, the specific value of #t6565575 compiles. xml : 6 : 4 : Invalid for given resource value. I was checking my colors.xml file, and wasn’t seeing any obvious issues: My “Eureka!” moment came from something I spotted out of the corner of my eye. My noggin was becoming raw from all the scratching. So I went back to my theme (as posted earlier in the article) and confirmed that colorPrimary was being set in the theme. In fact it’s really quite simple – it checks the theme attribute colorPrimary has been set.

Noggin scratching continued Deeper Down the rabbit holeĪ deep dive in to understanding precisely what checkAppCompatTheme() does was required. And the MaterialComponents theme that I was using for my app theme extends an AppCompat theme. So, the Material theme check passed whereas the AppCompt theme check failed.

#Android studio theme color code#

I stepped through the code using a debugger and verified that these checks were all performed and passed. There are other checks which all pass prior to this one. That method is being called from checkCompatibleTheme() The really odd thing is that checkAppCompatTheme() is the final line in checkCompatibleTheme().

The specific test that was failing is checkAppCompatTheme(). The stack trace from earlier shows that it was in the MaterialButton constructor that the theme validation was taking place.Īn internal MDC class named ThemeEnforcement was performing and failing the theme validation. The fact that my standard Button was being transformed to a MaterialButton showed that MDC inflation was happening. This actually involved some rather hack, convoluted code.Īt this point I started analysing how MDC works internally.

I verified that the theme being used to perform inflation was, in fact, the app theme. I confirmed that the MaterialComponents theme actually used an AppCompat theme as its parent. I confirmed that my dark theme also used a MaterialComponents theme as its parent. This theme does have a MaterialComponents theme as its parent.