Actual use case if developer settings in a common ...
# android
e
Actual use case if developer settings in a common settings fragment. I only want the developer settings views to be displayed in the
dev
flavor, but because the settings fragment is in common code, I have to make 0dp views with the same ID in the non-
dev
flavors so that I don't get an NPE (and if I try to guard against that the IDE complains because the synthetic variable is non-nullable)