Hi Xavier! I tried to enable proguard (w/o obfuscation) on my debug build with identical rules of those of my release build and get a ClassDefNotFoundException of a 3rd party library class right on the start of my instrumentation test, which I do not get when I run the proguarded release build of my app.
At first I thought this is an entirely unsupported use case, which is why I created a feature request for it on the bug tracker: https://code.google.com/p/android/issues/detail?id=77475, but reading that here apparently it is not. Since my project is private and reasonably large it would not make sense to go much into details at this point; instead, I would like to know more at first about the mechanics behind and if more specific configuration is needed which I might miss. I already figured out that giving my debug build an additional -injars ... setting for the "test app" that points to the created build/intermediates/classes-proguard/debug/classes.jar is pointless since this is the file proguard puts the remaining classes in for the debug apk itself. (I had this idea after reading http://blog.xebia.com/2013/08/04/android-tests-with-proguard) Any help would be greatly appreciated! Thanks, Thomas. Am Montag, 24. Februar 2014 18:19:35 UTC+1 schrieb Xavier Ducrohet: > > I think I added support for this, but I'll have to double check. You > shouldn't have to manually go and input this yourself. If the tested > variant is proguarded, the mapping file should be automatically injected > when compiling the test app. > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
