Dawid Weiss

Here is another repro for the same problem.

Hi Eric. I had to go back to this issue -- it's still not working in PG 6.1.1. I think it's a bug and it's also easily prevented -- see the patch here. https://github.com/dweiss/proguard/commit/6e729028a0c440dce90a40dc80137463a8c0fbef

This issue is describing the same problem: https://sourceforge.net/p/proguard/bugs/620/

interface methods, closures and applymapping don't work together (original method names kept invokedynamic)

A duplicate of https://sourceforge.net/p/proguard/bugs/536/

Java 11 is just around the corner, any chance to get support for that too? :)

Hi Eric. It's not really the case here -- the code hasn't changed at all, it's just missing some library classes that were used during the original obfuscation. The particular scenario we're using it in is this: we obfuscate the production library code and then obfuscate the tests for this library with the produced mapping. This way we can run the original set of tests against the obfuscated final jar, which is quite handy to capture problems with obfuscation itself early (and other issues as well)....

Just a quick follow-up. The same effect can actually happen in a different scenario as well - when proguard "shrinks" the set of library classes prior to obfuscation and discards certain classes (that used a mapping which eventually overlaps with the input classes).