Search code examples
androidproguardbuildconfig

Why should I keep BuildConfig in ProGuard?

I've met several proguard examples with these lines:

# Keep the BuildConfig
-keep class com.example.BuildConfig { *; }

I've run app with and without this line (of course, with my package) and haven't found any differences. I've also looked in generated/.../BuildConfig.java and there are no changes too.

What for do I need to keep my BuildConfig in ProGuard?

Thanks!

Solution

  • As with any other class, you need to -keep the class if you're accessing it indirectly via reflection so ProGuard won't obfuscate it or optimize it away as unused.

    Most often the access patterns with BuildConfig are direct without reflection so in those cases it's fine to have ProGuard process your BuildConfig, too.