proguard.cfg is not updated to match custom package names #9

choochootrain opened this Issue Dec 16, 2012 · 2 comments


None yet

2 participants


I noticed that when I used the site to generate an android package, it was failing the tests because proguard.cfg is not updated and roboguice could not find the constructors for BootstrapServiceProvider, ApiKeyProvider, and LogoutService.

-keep class**
-keepclassmembers class** { public <init>(...); }
-keep class** {
    *** set*(***);
    *** get*();

should also be changed to reflect the custom package name.


I changed the lines to match my package name and now it does pass all the default tests.


Good catch. I need to fix this in the generator code. I just ran into this myself this morning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment