Michael Rozumyanskiy

@AndroidDeveloperLB The library doesn't fully support obfuscation of AARs at the moment because of the issue @valeriyo mentioned above. Probably it can be supported but I don't like the idea...

I believe the root of the problem isn't in libraries but in multidex. Gradle Android plugin decides what classes to put into the main dex when building the APK. If...

@AndroidDeveloperLB What dependencies do you mean? Sorry, it seems I don't quite understand the problem you're describing.

@AndroidDeveloperLB If you add an AAR to the project as a maven dependency and this dependency contains a proper pom file transitive dependencies will be added automatically. And it works...

Actually @AndroidDeveloperLB told a quite an interesting thing. @valeriyo, how do you add the AAR file to the project? Is it a Maven artifact or just a file without pom.xml?

@AndroidDeveloperLB Usually you don't put the pom file into the repo but generate it instead. If you use the built-in Gradle's `maven-publish` plugin the pom file can be [customized via...

@AndroidDeveloperLB I think the string isn't obfuscated in your case because you apply `@Obfuscate` annotation to the `Keys` class. But the compiler inlines the string into the `MainActivity` class, which...

It's an unwanted but expected behavior. Obfuscation should work if the `@Obfuscate` annotation is applied to `MainActivity`. If it doesn't work reopen the issue please and I'll check why it...

It will work if the key isn't a compile time constant which is inlined by the compiler. So you can fix it by removing `const` or by converting the variable...

I've tried to build your project and as far as I can see it's obfuscated properly.