#751 Proguard doesn't import shrink - keep libraries

[i-pk-pjers-i]

Hi guys,

I believe I found an issue with ProGuard 6.1.0 on Ubuntu 18.04 (and 16.04) with Java 11. When I tell ProGuard to keep specific libraries in the Shrink tab and I save the config file, uplon importing the config file it seems to forget the specific libraries that I told it to keep.

Here is what it looks like before saving the file:

Here is what it looks like after importing the saved file:

Here is what the saved file looks like, to me the syntax looks correct:

# Keep - Libraries. Keep all public and protected classes, fields, and methods.
-keep public class org.apache.logging.**, com.lmax.** {
    public protected <fields>;
    public protected <methods>;
}

Thanks.

[Eric Lafortune]

Thanks for your report. It appears that, since ProGuard 6.0, configured class names aren't filled out in the text fields for boilerplate options like "Libraries". Instead, the options appear as custom options in the bottom panel. This doesn't introduce any major issues, but it isn't the intention.

[i-pk-pjers-i]

Hi,

Sorry, I'm not quite sure I understand. Is this something that can and possibly will be fixed - so that when I backup the configuration file it will still retain the checkmark and the specific classes I want filled out in the textbox after importing the configuration file? The way it functions right now, I have to manually enter those and select the checkbox for it to function the way I expect (and want) it to. It's not a huge deal to me, but it is an extra step that I'd rather not have to take each time.

Thanks.

[Eric Lafortune]

The GUI will be fixed, but for the time being, you can ignore the check box. Instead, you can select the entry in the bottom panel and edit it whenever necessary. The resulting configuration file is the relevant reference, and it seems to be okay. Does that make sense?

[i-pk-pjers-i]

Hi,

Yeah, I think I understand now. I'm glad to hear it will be fixed in the future.

Thanks.

[Eric Lafortune]

This bug has now been fixed for the upcoming ProGuard 6.2.