Krunal Charan

Hi, I have been through the same situation, and I tried a patch work on a branch of ProGuard 6.2.2 Branch: https://github.com/ckenny/proguard I have also created a Pull Request, https://github.com/Guardsquare/proguard/pull/31 The update introduced 3 new options, -dontresetmembernaming -dontresetclassnaming -dontresetpackagenaming In brief, these options will opt out the naming map's resetting logic and therefore the result will be all classes / packages will have unique names. (Attached the porguard-base-6.2.2.1.jar...